Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ef7c47d06eab5d3064b971f1801e0cad325a0c0dd59ed09cd8ab4cfda773e8e

Tx prefix hash: d7e75a1c9a1ad430d578781fd4171ad0e1b6bb1c31e47763bae72f6e35c8f056
Tx public key: 35c03b334d21b3258b679853b874fc88fd11353b8c7596b8a662c09061940565
Timestamp: 1704881530 Timestamp [UCT]: 2024-01-10 10:12:10 Age [y:d:h:m:s]: 01:123:14:10:37
Block: 932206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349449 RingCT/type: yes/0
Extra: 0135c03b334d21b3258b679853b874fc88fd11353b8c7596b8a662c0906194056502110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 180f5266efeb6d3f32d652fdcccd9a2d37a5abbb42edcc0e55bf50c5be13e8ab 0.600000000000 1390132 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": 932216, "vin": [ { "gen": { "height": 932206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "180f5266efeb6d3f32d652fdcccd9a2d37a5abbb42edcc0e55bf50c5be13e8ab" } } ], "extra": [ 1, 53, 192, 59, 51, 77, 33, 179, 37, 139, 103, 152, 83, 184, 116, 252, 136, 253, 17, 53, 59, 140, 117, 150, 184, 166, 98, 192, 144, 97, 148, 5, 101, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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