Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9dad410e9f2366f839d965c2d4c94ea848a858bd142d13deb44ea6ff64b18bb

Tx prefix hash: f773592aa84c0bc3d538a953c64a1a5a4263a2d6975eed20b944d7c9ed40511c
Tx public key: 6468559a7bad191afce98e0761177f77ea29ec7f45430d8f20d54d01884b558e
Timestamp: 1764844987 Timestamp [UTC]: 2025-12-04 10:43:07 Age [y:d:h:m:s]: 00:350:03:38:07
Block: 1426213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255736 RingCT/type: yes/0
Extra: 016468559a7bad191afce98e0761177f77ea29ec7f45430d8f20d54d01884b558e021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 875f782af1b4c3b29f1a15ff712030ece32e8dd85cad13c645fa5eb9a3538574 0.000600000000 1914902 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": 1426223, "vin": [ { "gen": { "height": 1426213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "875f782af1b4c3b29f1a15ff712030ece32e8dd85cad13c645fa5eb9a3538574" } } ], "extra": [ 1, 100, 104, 85, 154, 123, 173, 25, 26, 252, 233, 142, 7, 97, 23, 127, 119, 234, 41, 236, 127, 69, 67, 13, 143, 32, 213, 77, 1, 136, 75, 85, 142, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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: