Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7c10f85a98c5d973e0837aef4c27895c6eb517f3581c87d0aff6810f5301341

Tx prefix hash: f90fb24e06f7f6c46fd9a0793b8852c55995ae70a2d1f372956d8aacb1b7fb87
Tx public key: 1525d56ca5b736e6a34b044ded2dc157e76d6b953dd1224243c9e43dc553a5fd
Timestamp: 1708882818 Timestamp [UCT]: 2024-02-25 17:40:18 Age [y:d:h:m:s]: 01:074:06:01:31
Block: 965395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314096 RingCT/type: yes/0
Extra: 011525d56ca5b736e6a34b044ded2dc157e76d6b953dd1224243c9e43dc553a5fd0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0b4dbb36acab77125f32922e8ee9cc05b70e324f943217b3e521aef583c86e3 0.600000000000 1425146 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": 965405, "vin": [ { "gen": { "height": 965395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0b4dbb36acab77125f32922e8ee9cc05b70e324f943217b3e521aef583c86e3" } } ], "extra": [ 1, 21, 37, 213, 108, 165, 183, 54, 230, 163, 75, 4, 77, 237, 45, 193, 87, 231, 109, 107, 149, 61, 209, 34, 66, 67, 201, 228, 61, 197, 83, 165, 253, 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