Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 690290ccdf0245f750c80f52470e1236241a18f18ffa7ea90877c60c7be42e41

Tx prefix hash: f3d02e0a1ccd871b6f0c8014d18590d8652b23bbc95ed315951ef4bfd609f977
Tx public key: 9c23fbeadc270d48cc2dfebde913af65d744ced8745bde030e20ce1092e5e093
Timestamp: 1764472480 Timestamp [UTC]: 2025-11-30 03:14:40 Age [y:d:h:m:s]: 00:163:20:07:55
Block: 1423130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109297 RingCT/type: yes/0
Extra: 019c23fbeadc270d48cc2dfebde913af65d744ced8745bde030e20ce1092e5e09302110000000117b19132000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c823b8bf4314bee26d23b8d4e990416ab64fdfdef1bd5c67b180fa31bd6032e1 0.000600000000 1911733 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": 1423140, "vin": [ { "gen": { "height": 1423130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c823b8bf4314bee26d23b8d4e990416ab64fdfdef1bd5c67b180fa31bd6032e1" } } ], "extra": [ 1, 156, 35, 251, 234, 220, 39, 13, 72, 204, 45, 254, 189, 233, 19, 175, 101, 215, 68, 206, 216, 116, 91, 222, 3, 14, 32, 206, 16, 146, 229, 224, 147, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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: