Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979a0719f9370e80b252f77221a31cd4fa6703fb5175f1d78065fd1f36062616

Tx prefix hash: 59e3c0441fe52ad5c04eac3619d7232abbb9c1dac605296f6ce10a8be4f5f81f
Tx public key: e3e62d52e1cc02785d728b2aa43e82ed7c94fb0e533280efa712569e0e47db12
Timestamp: 1712059138 Timestamp [UCT]: 2024-04-02 11:58:58 Age [y:d:h:m:s]: 01:000:03:52:12
Block: 991694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261104 RingCT/type: yes/0
Extra: 01e3e62d52e1cc02785d728b2aa43e82ed7c94fb0e533280efa712569e0e47db120211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d95cc776755e891a28e9a73bddcc9ce63ebeada977791651dfda39373a97b23 0.600000000000 1452030 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": 991704, "vin": [ { "gen": { "height": 991694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d95cc776755e891a28e9a73bddcc9ce63ebeada977791651dfda39373a97b23" } } ], "extra": [ 1, 227, 230, 45, 82, 225, 204, 2, 120, 93, 114, 139, 42, 164, 62, 130, 237, 124, 148, 251, 14, 83, 50, 128, 239, 167, 18, 86, 158, 14, 71, 219, 18, 2, 17, 0, 0, 0, 5, 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