Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec42a29a2eb376d514777ec82603958dbc5fcdee3df8c28c8e03f1f44ff05b6c

Tx prefix hash: 26403d3436924826c4e579be1d26f244c98219eed4cacaed2162c494f6b4827f
Tx public key: c445938ae0271a37d4716e7ffe6b084e0c405f3100554adceab2a07c14fb5cd3
Timestamp: 1765437487 Timestamp [UCT]: 2025-12-11 07:18:07 Age [y:d:h:m:s]: 00:048:07:46:34
Block: 1431121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34427 RingCT/type: yes/0
Extra: 01c445938ae0271a37d4716e7ffe6b084e0c405f3100554adceab2a07c14fb5cd3021100000010d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce3dde528aeda756cd411f3950b4af55ad5c97c0da65accc723d34aa62547068 0.600000000000 1919876 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": 1431131, "vin": [ { "gen": { "height": 1431121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce3dde528aeda756cd411f3950b4af55ad5c97c0da65accc723d34aa62547068" } } ], "extra": [ 1, 196, 69, 147, 138, 224, 39, 26, 55, 212, 113, 110, 127, 254, 107, 8, 78, 12, 64, 95, 49, 0, 85, 74, 220, 234, 178, 160, 124, 20, 251, 92, 211, 2, 17, 0, 0, 0, 16, 214, 225, 157, 124, 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