Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dffa20dd9f54d45cef8ebc0007408d40ca6d8b37cd7db9a3d24a78d26c567bcb

Tx prefix hash: 0a318fa8771a3a31f60758c2247dec6063a03edceebc9bf59270b68fec0f25ee
Tx public key: cc5f5cd72f68d3e1ae5991525bce3d49c3c5efe050de04adf2cf2ec61287db22
Timestamp: 1703219592 Timestamp [UCT]: 2023-12-22 04:33:12 Age [y:d:h:m:s]: 01:346:10:42:36
Block: 918433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506483 RingCT/type: yes/0
Extra: 01cc5f5cd72f68d3e1ae5991525bce3d49c3c5efe050de04adf2cf2ec61287db2202110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de060f0840bd4ac8055655e1fcb8b0e3896da3a8bd04984377bb5b0646ed3c0e 0.600000000000 1376077 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": 918443, "vin": [ { "gen": { "height": 918433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de060f0840bd4ac8055655e1fcb8b0e3896da3a8bd04984377bb5b0646ed3c0e" } } ], "extra": [ 1, 204, 95, 92, 215, 47, 104, 211, 225, 174, 89, 145, 82, 91, 206, 61, 73, 195, 197, 239, 224, 80, 222, 4, 173, 242, 207, 46, 198, 18, 135, 219, 34, 2, 17, 0, 0, 0, 8, 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