Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cea5192f01af047ade618eae08595a23867b6c5ad4477b1638d09c4bd406d5f

Tx prefix hash: ace21750ec246bbeed239caba01e896de181a8196a728d0a8285e3ea0a29155d
Tx public key: 4807bfc681ffa64b1298ce1d3964379eec4ed2f037e6f897d15a1e5d578ef444
Timestamp: 1717932578 Timestamp [UCT]: 2024-06-09 11:29:38 Age [y:d:h:m:s]: 00:329:15:50:39
Block: 1040419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235601 RingCT/type: yes/0
Extra: 014807bfc681ffa64b1298ce1d3964379eec4ed2f037e6f897d15a1e5d578ef444021100000006d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1aa4f70d3492243597e0fdc1c841b4c05ca883e2111aef7d87bb3dca7154e05 0.600000000000 1509076 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": 1040429, "vin": [ { "gen": { "height": 1040419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1aa4f70d3492243597e0fdc1c841b4c05ca883e2111aef7d87bb3dca7154e05" } } ], "extra": [ 1, 72, 7, 191, 198, 129, 255, 166, 75, 18, 152, 206, 29, 57, 100, 55, 158, 236, 78, 210, 240, 55, 230, 248, 151, 209, 90, 30, 93, 87, 142, 244, 68, 2, 17, 0, 0, 0, 6, 215, 73, 245, 17, 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