Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a44186d13288c3c21fab39c7e446a9e9d2a0e27bf57cf9d3261c525e24765d1c

Tx prefix hash: de8d6bc2dc116b521c0266806a05f620aa37a3a078729a423040a2f042ddac38
Tx public key: c0146bea60cb92027f79c814151457e5e68125572002f396c70bddd22ba505d4
Timestamp: 1728904648 Timestamp [UCT]: 2024-10-14 11:17:28 Age [y:d:h:m:s]: 00:190:10:38:30
Block: 1131381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135892 RingCT/type: yes/0
Extra: 01c0146bea60cb92027f79c814151457e5e68125572002f396c70bddd22ba505d4021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2093038d89330bf9dc59f18cc88ca9ba5965f02eefdbb7c5696834d8d33b597 0.600000000000 1614280 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": 1131391, "vin": [ { "gen": { "height": 1131381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2093038d89330bf9dc59f18cc88ca9ba5965f02eefdbb7c5696834d8d33b597" } } ], "extra": [ 1, 192, 20, 107, 234, 96, 203, 146, 2, 127, 121, 200, 20, 21, 20, 87, 229, 230, 129, 37, 87, 32, 2, 243, 150, 199, 11, 221, 210, 43, 165, 5, 212, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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