Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0cbcfb4b69ad00bf357a6aeeb82ecd7236ca1f963f9664d0edf90c64592e77c

Tx prefix hash: cc8449b1a247152be3d72a1f7c20fcf59386a1c7fc75c01e7b1a644ce7ab9346
Tx public key: d62001d82f5c4251f7a8a131799085842ae2f909d59a578fdab38070ecee0b84
Timestamp: 1742261454 Timestamp [UTC]: 2025-03-18 01:30:54 Age [y:d:h:m:s]: 01:248:11:30:14
Block: 1241652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441766 RingCT/type: yes/0
Extra: 01d62001d82f5c4251f7a8a131799085842ae2f909d59a578fdab38070ecee0b840211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2ccb46df49ca25171fd9384d912e998150029d8aeb4a272d1c8f4b501fb293c1 0.000600000000 1728625 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": 1241662, "vin": [ { "gen": { "height": 1241652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ccb46df49ca25171fd9384d912e998150029d8aeb4a272d1c8f4b501fb293c1" } } ], "extra": [ 1, 214, 32, 1, 216, 47, 92, 66, 81, 247, 168, 161, 49, 121, 144, 133, 132, 42, 226, 249, 9, 213, 154, 87, 143, 218, 179, 128, 112, 236, 238, 11, 132, 2, 17, 0, 0, 0, 1, 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: