Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c55a13118f744118dd9ad1dc3f4b60eaf8a8c49f5a613f1f57b8dc3f4ac4cc78

Tx prefix hash: f7615e60f54ffabe79a56ae36511dbbd5c3718d15db662431c2eb44c3d00fffa
Tx public key: 0c250722cec14a303247aebbf9fc17e06ba285f7d85f6f298549fb017b913a13
Timestamp: 1715176545 Timestamp [UCT]: 2024-05-08 13:55:45 Age [y:d:h:m:s]: 00:340:00:00:43
Block: 1017582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243021 RingCT/type: yes/0
Extra: 010c250722cec14a303247aebbf9fc17e06ba285f7d85f6f298549fb017b913a1302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf6c858d9dd9ab1856f34e259e6f8907e514d1bcfa6db830be90e3af72167558 0.600000000000 1481365 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": 1017592, "vin": [ { "gen": { "height": 1017582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf6c858d9dd9ab1856f34e259e6f8907e514d1bcfa6db830be90e3af72167558" } } ], "extra": [ 1, 12, 37, 7, 34, 206, 193, 74, 48, 50, 71, 174, 187, 249, 252, 23, 224, 107, 162, 133, 247, 216, 95, 111, 41, 133, 73, 251, 1, 123, 145, 58, 19, 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