Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ac9cf7d05f4efb045d7c70c92e3977705a3dc30ad10163c951439becc0d463d

Tx prefix hash: 124f8dfdad6515c862902c112d4064537133326c1ec2cde66a40031eec75b60f
Tx public key: 35adad80cbd352f4d3927c393516b51b9f9266967f0b44a6353280e8f87b9d80
Timestamp: 1773951245 Timestamp [UTC]: 2026-03-19 20:14:05 Age [y:d:h:m:s]: 00:052:03:42:38
Block: 1501430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30003 RingCT/type: yes/0
Extra: 0135adad80cbd352f4d3927c393516b51b9f9266967f0b44a6353280e8f87b9d80021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 61cdfab88a0bd10ffd4ee6011b03bec701682da1ba504bf1ef07e616c306e186 0.000600000000 1991114 of 15 -

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": 1501440, "vin": [ { "gen": { "height": 1501430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61cdfab88a0bd10ffd4ee6011b03bec701682da1ba504bf1ef07e616c306e186" } } ], "extra": [ 1, 53, 173, 173, 128, 203, 211, 82, 244, 211, 146, 124, 57, 53, 22, 181, 27, 159, 146, 102, 150, 127, 11, 68, 166, 53, 50, 128, 232, 248, 123, 157, 128, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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) | monero version: