Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0db0315c5c27927c30e5380ae121706aca7c0bc54acc58f14341f2062d040f0

Tx prefix hash: c083506cf7553868a5e1bf29f173d60303b21ffde754fd10762f9fb52e67d7b5
Tx public key: a30323fef9c490d42a7ef4b720257a4fc1c036440cdaef88ea904a40e3fc51e0
Timestamp: 1749477465 Timestamp [UCT]: 2025-06-09 13:57:45 Age [y:d:h:m:s]: 00:158:10:58:58
Block: 1301391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110926 RingCT/type: yes/0
Extra: 01a30323fef9c490d42a7ef4b720257a4fc1c036440cdaef88ea904a40e3fc51e002110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cdb3a96f950799a8baa28c0742ee06b017d47715af958d7ce6d03f67af3deaf 0.600000000000 1788948 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 dinasty-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": 1301401, "vin": [ { "gen": { "height": 1301391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cdb3a96f950799a8baa28c0742ee06b017d47715af958d7ce6d03f67af3deaf" } } ], "extra": [ 1, 163, 3, 35, 254, 249, 196, 144, 212, 42, 126, 244, 183, 32, 37, 122, 79, 193, 192, 54, 68, 12, 218, 239, 136, 234, 144, 74, 64, 227, 252, 81, 224, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8