Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ddda9d95344e56258afe20a4e805d933e08bf38669a73e47b01bba0ea3bd589

Tx prefix hash: d28e26f0b879fb10a032f332bd241a71730403775f93c43146ecebc776dc2405
Tx public key: 0ce5d77c9ea067b99679637efb73c2c5a1b301c6631ea4dd9d31bfad3a5f67f3
Timestamp: 1734342784 Timestamp [UCT]: 2024-12-16 09:53:04 Age [y:d:h:m:s]: 00:108:20:44:46
Block: 1176372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77578 RingCT/type: yes/0
Extra: 010ce5d77c9ea067b99679637efb73c2c5a1b301c6631ea4dd9d31bfad3a5f67f3021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47ced9fd2e0c951b8eb43bb486e4222edbda2553c8519d9d858ad775e240f6fe 0.600000000000 1662703 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": 1176382, "vin": [ { "gen": { "height": 1176372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47ced9fd2e0c951b8eb43bb486e4222edbda2553c8519d9d858ad775e240f6fe" } } ], "extra": [ 1, 12, 229, 215, 124, 158, 160, 103, 185, 150, 121, 99, 126, 251, 115, 194, 197, 161, 179, 1, 198, 99, 30, 164, 221, 157, 49, 191, 173, 58, 95, 103, 243, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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