Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 015ae6d618fb9ca2f15b879c69d3dac1e7e915d263b96a00ed26727d0edc8897

Tx prefix hash: 405f457eb5e9974f508f508b97fe081b0fbc35ffe0c49b4766756c5b8c616d43
Tx public key: 01662f5bc139af35378c6c05351586d73919db5b80ca81ce3a40f71bd7226481
Timestamp: 1712950717 Timestamp [UCT]: 2024-04-12 19:38:37 Age [y:d:h:m:s]: 01:292:11:32:40
Block: 999092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467653 RingCT/type: yes/0
Extra: 0101662f5bc139af35378c6c05351586d73919db5b80ca81ce3a40f71bd72264810211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce4c4443eaf9b3d23bdd447dd957ef7a3c82d0c87c81a247135aeb5a2f7b9adf 0.600000000000 1459568 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": 999102, "vin": [ { "gen": { "height": 999092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce4c4443eaf9b3d23bdd447dd957ef7a3c82d0c87c81a247135aeb5a2f7b9adf" } } ], "extra": [ 1, 1, 102, 47, 91, 193, 57, 175, 53, 55, 140, 108, 5, 53, 21, 134, 215, 57, 25, 219, 91, 128, 202, 129, 206, 58, 64, 247, 27, 215, 34, 100, 129, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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