Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 034372eb00c8310d857737b84f51808184092a9e21ceb1422ebca4afdca64cd0

Tx prefix hash: 2016d765463fd9c5960d0757359f92c755f1a3b6d094809a67f4fcced50e7cf5
Tx public key: df0af0bb1b04e1ff84268b0acfd91daa7a1f13351df8b6abc733a157fff76266
Timestamp: 1735004084 Timestamp [UCT]: 2024-12-24 01:34:44 Age [y:d:h:m:s]: 00:003:13:24:31
Block: 1181835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2534 RingCT/type: yes/0
Extra: 01df0af0bb1b04e1ff84268b0acfd91daa7a1f13351df8b6abc733a157fff762660211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ee7c594a8d2eb3d0879a97b284b486e6141d4a6733021edd529d5a70a1e2bb3 0.600000000000 1668264 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": 1181845, "vin": [ { "gen": { "height": 1181835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ee7c594a8d2eb3d0879a97b284b486e6141d4a6733021edd529d5a70a1e2bb3" } } ], "extra": [ 1, 223, 10, 240, 187, 27, 4, 225, 255, 132, 38, 139, 10, 207, 217, 29, 170, 122, 31, 19, 53, 29, 248, 182, 171, 199, 51, 161, 87, 255, 247, 98, 102, 2, 17, 0, 0, 0, 3, 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