Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11c762e532b35ea00fc3beeb2ef893701b090c259b1a98fada65b9ab616d7a30

Tx prefix hash: bb5918fe646dca5cc20409b390cacc5663029645927fadd9f9f4de9a505f6e85
Tx public key: 964bfba0eae54e3827528c532fe1618f6f0f25c27b6aa9317acb18bc29cbe8cb
Timestamp: 1703888308 Timestamp [UCT]: 2023-12-29 22:18:28 Age [y:d:h:m:s]: 01:026:08:37:25
Block: 923976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280144 RingCT/type: yes/0
Extra: 01964bfba0eae54e3827528c532fe1618f6f0f25c27b6aa9317acb18bc29cbe8cb021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66ee8c417875f300a4b6cff461654ea291acd815621b733db65cd213215b56e9 0.600000000000 1381718 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": 923986, "vin": [ { "gen": { "height": 923976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66ee8c417875f300a4b6cff461654ea291acd815621b733db65cd213215b56e9" } } ], "extra": [ 1, 150, 75, 251, 160, 234, 229, 78, 56, 39, 82, 140, 83, 47, 225, 97, 143, 111, 15, 37, 194, 123, 106, 169, 49, 122, 203, 24, 188, 41, 203, 232, 203, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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