Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ec4932fe1ee1909e23a2844d9724cf97e2499c85ee2539b47699ec1ce0212ce

Tx prefix hash: 836f6ebee30fef38f49c91db43b17dff130e3bfd72895b29d91790319f9f03c3
Tx public key: 3723804b9ed895d6486383b2f8e9b6d2e811c7c9c242fc54d0c8617d0b15c7c1
Timestamp: 1715693604 Timestamp [UCT]: 2024-05-14 13:33:24 Age [y:d:h:m:s]: 00:241:16:22:29
Block: 1021859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172973 RingCT/type: yes/0
Extra: 013723804b9ed895d6486383b2f8e9b6d2e811c7c9c242fc54d0c8617d0b15c7c102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c45f158ef31400708e59e486ecf13376d99e369d30133591cabeef44d714b7d9 0.600000000000 1486290 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": 1021869, "vin": [ { "gen": { "height": 1021859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c45f158ef31400708e59e486ecf13376d99e369d30133591cabeef44d714b7d9" } } ], "extra": [ 1, 55, 35, 128, 75, 158, 216, 149, 214, 72, 99, 131, 178, 248, 233, 182, 210, 232, 17, 199, 201, 194, 66, 252, 84, 208, 200, 97, 125, 11, 21, 199, 193, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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