Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b452c8fe93a6b3c0615b7aa3fca3ffe85fa614778384562b9370ab5f53fc16e

Tx prefix hash: b4bd6133d76914ffb69f99efcca7cabd91c7ac969c89f5449d9e611f6c2c49fa
Tx public key: a57290d44d74476a83d0bc9881d4f0a53250ac00df3e05293a8cd0c3e32b8470
Timestamp: 1713940923 Timestamp [UCT]: 2024-04-24 06:42:03 Age [y:d:h:m:s]: 00:204:20:14:22
Block: 1007325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146623 RingCT/type: yes/0
Extra: 01a57290d44d74476a83d0bc9881d4f0a53250ac00df3e05293a8cd0c3e32b847002110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79dccfcd992316dbfb3f0827660cf5a8fc1c0595f9779f3cfad180f586021f59 0.600000000000 1468629 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": 1007335, "vin": [ { "gen": { "height": 1007325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79dccfcd992316dbfb3f0827660cf5a8fc1c0595f9779f3cfad180f586021f59" } } ], "extra": [ 1, 165, 114, 144, 212, 77, 116, 71, 106, 131, 208, 188, 152, 129, 212, 240, 165, 50, 80, 172, 0, 223, 62, 5, 41, 58, 140, 208, 195, 227, 43, 132, 112, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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