Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d13a5e10cfe6ccc2704a696f91035dac8af9e7e7a9f71da12d0fd6d3c388e6cf

Tx prefix hash: dbfb7670af1f81fdecf4308d68507e631d7e96ab5f11b2b02bd0f16dcbaeda8d
Tx public key: c2d3ed840de7fe74a62678c46bfcd461315299ce54819da6f4ad56e1e49fde2f
Timestamp: 1731383819 Timestamp [UCT]: 2024-11-12 03:56:59 Age [y:d:h:m:s]: 00:152:18:06:33
Block: 1151838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109025 RingCT/type: yes/0
Extra: 01c2d3ed840de7fe74a62678c46bfcd461315299ce54819da6f4ad56e1e49fde2f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5591233738741e59e87293666032263e66c19e1ffe5f32d759e0143ad7721f12 0.600000000000 1637421 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": 1151848, "vin": [ { "gen": { "height": 1151838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5591233738741e59e87293666032263e66c19e1ffe5f32d759e0143ad7721f12" } } ], "extra": [ 1, 194, 211, 237, 132, 13, 231, 254, 116, 166, 38, 120, 196, 107, 252, 212, 97, 49, 82, 153, 206, 84, 129, 157, 166, 244, 173, 86, 225, 228, 159, 222, 47, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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