Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6412b8aee91b72928d462dddeacf9735890440363d4b5feb809f8eb414f1ade

Tx prefix hash: 09efec5ceca877b9050118c20e3297ea0d0ee89bfb8da97856c812b55f81db02
Tx public key: 0ecd072a0a0fb5239f2bafbfdcc1712acd841d07fe93fccfe7004e6670f41da0
Timestamp: 1703558130 Timestamp [UCT]: 2023-12-26 02:35:30 Age [y:d:h:m:s]: 01:124:01:16:42
Block: 921242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349798 RingCT/type: yes/0
Extra: 010ecd072a0a0fb5239f2bafbfdcc1712acd841d07fe93fccfe7004e6670f41da00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49339c32f9e669ce2f8b8ea5e988b6ecd6535ec90e8a1bff2dd7847793ce0ba1 0.600000000000 1378928 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": 921252, "vin": [ { "gen": { "height": 921242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49339c32f9e669ce2f8b8ea5e988b6ecd6535ec90e8a1bff2dd7847793ce0ba1" } } ], "extra": [ 1, 14, 205, 7, 42, 10, 15, 181, 35, 159, 43, 175, 191, 220, 193, 113, 42, 205, 132, 29, 7, 254, 147, 252, 207, 231, 0, 78, 102, 112, 244, 29, 160, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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