Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 816039fcc0c1cc10b3655e96c1a4120970ba59ab32f73e4817daf7327a60304b

Tx prefix hash: 2418acc1dc9e9995c61e84246a79644cf3efbc7b1842441a4e1c59080548ff78
Tx public key: 14c9ee218ae858e5df1dbac1fd4ba448045516a4bf23a2393983efe71c7ccf67
Timestamp: 1755060996 Timestamp [UCT]: 2025-08-13 04:56:36 Age [y:d:h:m:s]: 00:105:09:36:06
Block: 1345843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74751 RingCT/type: yes/0
Extra: 0114c9ee218ae858e5df1dbac1fd4ba448045516a4bf23a2393983efe71c7ccf67021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e26772e69fc11e3044d2696d0037b1e9c5a1f817c9256899c5778c9fd69216d 0.600000000000 1833738 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": 1345853, "vin": [ { "gen": { "height": 1345843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e26772e69fc11e3044d2696d0037b1e9c5a1f817c9256899c5778c9fd69216d" } } ], "extra": [ 1, 20, 201, 238, 33, 138, 232, 88, 229, 223, 29, 186, 193, 253, 75, 164, 72, 4, 85, 22, 164, 191, 35, 162, 57, 57, 131, 239, 231, 28, 124, 207, 103, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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