Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c9a4e2f52ec70d30bb5152d5465e7238268dc57fb0c1a5f1c86803df61778c0

Tx prefix hash: 9b247789313a15797485de720b8a2ee2dfbc9aadfcb54ef3e51a04f60acfa1b5
Tx public key: ae9b351de61a3d97fbaddae7d87bd07241b8ad53abd93ea359599a880129c066
Timestamp: 1716717161 Timestamp [UCT]: 2024-05-26 09:52:41 Age [y:d:h:m:s]: 00:333:14:59:19
Block: 1030349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238452 RingCT/type: yes/0
Extra: 01ae9b351de61a3d97fbaddae7d87bd07241b8ad53abd93ea359599a880129c06602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5acff3d101979a93f773ce49111e0a463e4e117b90090f501f98725e906c6a4 0.600000000000 1498604 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": 1030359, "vin": [ { "gen": { "height": 1030349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5acff3d101979a93f773ce49111e0a463e4e117b90090f501f98725e906c6a4" } } ], "extra": [ 1, 174, 155, 53, 29, 230, 26, 61, 151, 251, 173, 218, 231, 216, 123, 208, 114, 65, 184, 173, 83, 171, 217, 62, 163, 89, 89, 154, 136, 1, 41, 192, 102, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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