Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5948d3dd5fa4c033fefdac1fdc8ec483b270b12ee6d7f0f5fd7882492996a4c

Tx prefix hash: bce923b46b39bb399e3c24a6c8672cf31c720073c7fb04fc2ffbf2d068dc7f45
Tx public key: 5c8c24f958adeac10b4a94ce429a37408356b57e18d3590d260280c9e986a283
Timestamp: 1727493488 Timestamp [UCT]: 2024-09-28 03:18:08 Age [y:d:h:m:s]: 00:184:03:55:22
Block: 1119683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131420 RingCT/type: yes/0
Extra: 015c8c24f958adeac10b4a94ce429a37408356b57e18d3590d260280c9e986a28302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb0da90e765f9dc2bc2a705144594590524201dec6e665c819d880d12e50d99 0.600000000000 1601330 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": 1119693, "vin": [ { "gen": { "height": 1119683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb0da90e765f9dc2bc2a705144594590524201dec6e665c819d880d12e50d99" } } ], "extra": [ 1, 92, 140, 36, 249, 88, 173, 234, 193, 11, 74, 148, 206, 66, 154, 55, 64, 131, 86, 181, 126, 24, 211, 89, 13, 38, 2, 128, 201, 233, 134, 162, 131, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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