Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e631cdd84876229db3acc8f4e97d2a4f168070ff4604091a3de3fb4367977f7b

Tx prefix hash: 07638c29970d849c636491dc4d218fddb5b6e096c2ac997919109d2ab7998bc5
Tx public key: 0c798da2f0df3d2ee50fce27cd1d0e360d7a27d16622dd45a51f0ee6fe5eaaa3
Timestamp: 1751666646 Timestamp [UCT]: 2025-07-04 22:04:06 Age [y:d:h:m:s]: 00:133:02:01:36
Block: 1318870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93419 RingCT/type: yes/0
Extra: 010c798da2f0df3d2ee50fce27cd1d0e360d7a27d16622dd45a51f0ee6fe5eaaa302110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e954c2364a88961df4449c726003a0f2c2cf960e741df49b122a6864ff58bb7b 0.600000000000 1806557 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": 1318880, "vin": [ { "gen": { "height": 1318870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e954c2364a88961df4449c726003a0f2c2cf960e741df49b122a6864ff58bb7b" } } ], "extra": [ 1, 12, 121, 141, 162, 240, 223, 61, 46, 229, 15, 206, 39, 205, 29, 14, 54, 13, 122, 39, 209, 102, 34, 221, 69, 165, 31, 14, 230, 254, 94, 170, 163, 2, 17, 0, 0, 0, 2, 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