Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c54e121a9fd5691698ecdc1b95ddb01c3fe14f309f8008f1d024ac21c3aba6f8

Tx prefix hash: d7632ac883428a04e10b09d879def6672833b78bc94f47f6d3ba64b531875efb
Tx public key: 63d14b1ea5ec630e2580142fd150ae267e827c0eb65fbcde6c8d71afd127a4ee
Timestamp: 1733220250 Timestamp [UCT]: 2024-12-03 10:04:10 Age [y:d:h:m:s]: 00:128:13:45:48
Block: 1167060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91685 RingCT/type: yes/0
Extra: 0163d14b1ea5ec630e2580142fd150ae267e827c0eb65fbcde6c8d71afd127a4ee021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1afcce35e71f9c3725289ad340d33964c147a3445eb2fbb2c4d81d1740b2cf61 0.600000000000 1652753 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": 1167070, "vin": [ { "gen": { "height": 1167060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1afcce35e71f9c3725289ad340d33964c147a3445eb2fbb2c4d81d1740b2cf61" } } ], "extra": [ 1, 99, 209, 75, 30, 165, 236, 99, 14, 37, 128, 20, 47, 209, 80, 174, 38, 126, 130, 124, 14, 182, 95, 188, 222, 108, 141, 113, 175, 209, 39, 164, 238, 2, 17, 0, 0, 0, 1, 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