Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 792eb798973c47b8240188cfdd2fac704aa146597b467846c5315d4b3a447a52

Tx prefix hash: ba20829f9c995e7fea55c4ed12238855767a370d905beab2d15b746214bde924
Tx public key: 7e10b5f6bb581a4b8178e905b6e06cc9322ece97833aa7d9e7ea15911ec20d5f
Timestamp: 1708235158 Timestamp [UCT]: 2024-02-18 05:45:58 Age [y:d:h:m:s]: 01:044:16:41:40
Block: 960019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292964 RingCT/type: yes/0
Extra: 017e10b5f6bb581a4b8178e905b6e06cc9322ece97833aa7d9e7ea15911ec20d5f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6979b2315eed2eb4479a396ee1b91d8dbee71342088faf35d89aa6108fde448b 0.600000000000 1419578 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": 960029, "vin": [ { "gen": { "height": 960019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6979b2315eed2eb4479a396ee1b91d8dbee71342088faf35d89aa6108fde448b" } } ], "extra": [ 1, 126, 16, 181, 246, 187, 88, 26, 75, 129, 120, 233, 5, 182, 224, 108, 201, 50, 46, 206, 151, 131, 58, 167, 217, 231, 234, 21, 145, 30, 194, 13, 95, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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