Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63175448ac10a0708769067f2aa43367d3fdf281fe430af69d9de17b59d9c033

Tx prefix hash: 9936d62f957590bd69cbafb85b6efea3f603381dafc943b1e4e260e03b678f68
Tx public key: ad98f88a9f830f3dbc27b4d3437129f25785ef12837cba020b83793e9a3a3fd3
Timestamp: 1696564263 Timestamp [UCT]: 2023-10-06 03:51:03 Age [y:d:h:m:s]: 01:098:14:51:26
Block: 863458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331748 RingCT/type: yes/0
Extra: 01ad98f88a9f830f3dbc27b4d3437129f25785ef12837cba020b83793e9a3a3fd3021100000012faf35c9c000000000000000000

1 output(s) for total of 0.845289053000 dcy

stealth address amount amount idx
00: 84230df35630b661aedfe28c689861526f518fb077cf541edcbb01f541ec5ec8 0.845289053000 1317914 of 0

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": 863468, "vin": [ { "gen": { "height": 863458 } } ], "vout": [ { "amount": 845289053, "target": { "key": "84230df35630b661aedfe28c689861526f518fb077cf541edcbb01f541ec5ec8" } } ], "extra": [ 1, 173, 152, 248, 138, 159, 131, 15, 61, 188, 39, 180, 211, 67, 113, 41, 242, 87, 133, 239, 18, 131, 124, 186, 2, 11, 131, 121, 62, 154, 58, 63, 211, 2, 17, 0, 0, 0, 18, 250, 243, 92, 156, 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