Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0310dbc15e1c3714636ea807db3bc85f62e8f0da3077cc6fe1b07646d46a357

Tx prefix hash: d076065ecf25492ab622504022293949711cadc5cc14f6e15bbd79bdd23415cb
Tx public key: 884e924c2a8a58c8a442b2b993c3df21e405430458a8f460bc4334ad5dee1f33
Timestamp: 1755264968 Timestamp [UCT]: 2025-08-15 13:36:08 Age [y:d:h:m:s]: 00:043:05:10:47
Block: 1347246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30509 RingCT/type: yes/0
Extra: 01884e924c2a8a58c8a442b2b993c3df21e405430458a8f460bc4334ad5dee1f33021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa09d9425af4a8ddd1bb15fe6e388ebfc8ad49bedd912cd5634e0f6de2748fc8 0.600000000000 1835161 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": 1347256, "vin": [ { "gen": { "height": 1347246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa09d9425af4a8ddd1bb15fe6e388ebfc8ad49bedd912cd5634e0f6de2748fc8" } } ], "extra": [ 1, 136, 78, 146, 76, 42, 138, 88, 200, 164, 66, 178, 185, 147, 195, 223, 33, 228, 5, 67, 4, 88, 168, 244, 96, 188, 67, 52, 173, 93, 238, 31, 51, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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