Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 345fc5cab25d948f6d00686e9420aa20923951f8370e2702c02b356a30ff2989

Tx prefix hash: 97de3b7f205deb2cad72872e6dbb99eb7e78a061784b13a169a60f562687a437
Tx public key: bad2f423f52edeae96ca1c38b193cada1719f0f035a2e6f6e86c945de0d2aebc
Timestamp: 1647433927 Timestamp [UCT]: 2022-03-16 12:32:07 Age [y:d:h:m:s]: 02:282:12:36:11
Block: 459675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721457 RingCT/type: yes/0
Extra: 01bad2f423f52edeae96ca1c38b193cada1719f0f035a2e6f6e86c945de0d2aebc02110000001fd3fcec30000000000000000000

1 output(s) for total of 18.403963403000 dcy

stealth address amount amount idx
00: fe6c63a8899ca3d73bac5307e35d735545dc20921104907092a17322977481c5 18.403963403000 876476 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": 459685, "vin": [ { "gen": { "height": 459675 } } ], "vout": [ { "amount": 18403963403, "target": { "key": "fe6c63a8899ca3d73bac5307e35d735545dc20921104907092a17322977481c5" } } ], "extra": [ 1, 186, 210, 244, 35, 245, 46, 222, 174, 150, 202, 28, 56, 177, 147, 202, 218, 23, 25, 240, 240, 53, 162, 230, 246, 232, 108, 148, 93, 224, 210, 174, 188, 2, 17, 0, 0, 0, 31, 211, 252, 236, 48, 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