Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6033b652cccdd48e0add4e46544cc57d07f27c107a7ad238f32c0c73df4e505

Tx prefix hash: 956ea4f4ce7034faed911111cadd42914963cea0e96df55c7f0e079608a19ba4
Tx public key: f5d578b8484c471cb2848fa53368a5fa8e47c7416adb32d3d0efbb75fb6c19f7
Timestamp: 1720022849 Timestamp [UCT]: 2024-07-03 16:07:29 Age [y:d:h:m:s]: 00:351:06:44:40
Block: 1057744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250912 RingCT/type: yes/0
Extra: 01f5d578b8484c471cb2848fa53368a5fa8e47c7416adb32d3d0efbb75fb6c19f702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5f196613dc05245e5d170ffcd6c4a24082e54260ee06daa4a81e6aade341d81 0.600000000000 1528185 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": 1057754, "vin": [ { "gen": { "height": 1057744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5f196613dc05245e5d170ffcd6c4a24082e54260ee06daa4a81e6aade341d81" } } ], "extra": [ 1, 245, 213, 120, 184, 72, 76, 71, 28, 178, 132, 143, 165, 51, 104, 165, 250, 142, 71, 199, 65, 106, 219, 50, 211, 208, 239, 187, 117, 251, 108, 25, 247, 2, 17, 0, 0, 0, 3, 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