Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8c7739355909661f51a8f2fed1e4c2cf63c78337c6d66ec18f5c2750cae8ddd

Tx prefix hash: e11d7558d9272b645b75ee23edae702aafe3da2ffd7b963442fad9c698eb6b19
Tx public key: 1db472ad2e383880a78dc8ce59adba716d22a63d79f111c693dee3888fc94ce9
Timestamp: 1709054215 Timestamp [UCT]: 2024-02-27 17:16:55 Age [y:d:h:m:s]: 01:111:20:04:19
Block: 966821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340844 RingCT/type: yes/0
Extra: 011db472ad2e383880a78dc8ce59adba716d22a63d79f111c693dee3888fc94ce90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91730dcf0e7c7a90c5a5e65eb2c8d4167b1fa0ef418e064e6c540ad09ce8f1af 0.600000000000 1426592 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": 966831, "vin": [ { "gen": { "height": 966821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91730dcf0e7c7a90c5a5e65eb2c8d4167b1fa0ef418e064e6c540ad09ce8f1af" } } ], "extra": [ 1, 29, 180, 114, 173, 46, 56, 56, 128, 167, 141, 200, 206, 89, 173, 186, 113, 109, 34, 166, 61, 121, 241, 17, 198, 147, 222, 227, 136, 143, 201, 76, 233, 2, 17, 0, 0, 0, 1, 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