Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2b248d7e0e94d21e250af48d238b1fb14d284dabe7e962ee4e72c5ea5d94daa2

Tx prefix hash: effa18d25d7942e6df014f88ada400b5636b3847c6d13216c0e20b592f4323e0
Tx public key: a1e5ddfb9c3f6e3023015c372b2404a9742bfd9ac3f8d3495a144df2fc755508
Timestamp: 1574629778 Timestamp [UTC]: 2019-11-24 21:09:38 Age [y:d:h:m:s]: 06:088:17:54:10
Block: 16684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1464589 RingCT/type: yes/0
Extra: 01a1e5ddfb9c3f6e3023015c372b2404a9742bfd9ac3f8d3495a144df2fc755508021100000001f95225a5000000000000000000

1 output(s) for total of 0.540424238673 xmr

stealth address amount amount idx tag
00: 75ed42c59e4922090119788cb432c9fb57dac706a573a03c359f61c8f297556e 0.540424238673 23540 of 0 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 16694, "vin": [ { "gen": { "height": 16684 } } ], "vout": [ { "amount": 540424238673, "target": { "key": "75ed42c59e4922090119788cb432c9fb57dac706a573a03c359f61c8f297556e" } } ], "extra": [ 1, 161, 229, 221, 251, 156, 63, 110, 48, 35, 1, 92, 55, 43, 36, 4, 169, 116, 43, 253, 154, 195, 248, 211, 73, 90, 20, 77, 242, 252, 117, 85, 8, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369