Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61facaa9ececfcf701db2f1a6fc4b14f7cae05c1e909e1e614cfc3d616bddc12

Tx prefix hash: 7bddf93ccb06d2649a0e54ea05075200d827c531932c74557114fa4086384521
Tx public key: 670e970286c59ebcb9e53836545880bfd5adc80b9c4d19ad309be3986be8631f
Timestamp: 1771528377 Timestamp [UTC]: 2026-02-19 19:12:57 Age [y:d:h:m:s]: 00:268:16:13:52
Block: 1481402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197458 RingCT/type: yes/0
Extra: 01670e970286c59ebcb9e53836545880bfd5adc80b9c4d19ad309be3986be8631f021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a346d7f1afb0f9aa2e9ab85e5bacc9ffff0e641364b954a1240175c05dec8605 0.000600000000 1970778 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": 1481412, "vin": [ { "gen": { "height": 1481402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a346d7f1afb0f9aa2e9ab85e5bacc9ffff0e641364b954a1240175c05dec8605" } } ], "extra": [ 1, 103, 14, 151, 2, 134, 197, 158, 188, 185, 229, 56, 54, 84, 88, 128, 191, 213, 173, 200, 11, 156, 77, 25, 173, 48, 155, 227, 152, 107, 232, 99, 31, 2, 17, 0, 0, 0, 1, 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: