Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb62b72833cf0c0b8fa43953a0aeb3d4786b312880b15fb29bd4614907460ec9

Tx prefix hash: a21b1203ed7f0001a95aea7b55c5aa1ae447539b51d0ebd0dce4d9fa069bd025
Tx public key: 704ecce3d2df479f8a5b8e7985a053579a8ac0843f0d1de520ce1aeff44e17cf
Timestamp: 1737718483 Timestamp [UTC]: 2025-01-24 11:34:43 Age [y:d:h:m:s]: 01:300:14:42:39
Block: 1204254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478843 RingCT/type: yes/0
Extra: 01704ecce3d2df479f8a5b8e7985a053579a8ac0843f0d1de520ce1aeff44e17cf0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a6dfc72c998ffe08ac0e5e52672a0941b532132744a135381d1d81ec2b0fad78 0.000600000000 1690939 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": 1204264, "vin": [ { "gen": { "height": 1204254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6dfc72c998ffe08ac0e5e52672a0941b532132744a135381d1d81ec2b0fad78" } } ], "extra": [ 1, 112, 78, 204, 227, 210, 223, 71, 159, 138, 91, 142, 121, 133, 160, 83, 87, 154, 138, 192, 132, 63, 13, 29, 229, 32, 206, 26, 239, 244, 78, 23, 207, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: