Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed2de424560af6030bc1db8af023c08c02334fa41368d8d9b3d44ca5e458550c

Tx prefix hash: 57a27793c3160769e2de67be280d43e527966c3f081e008c844c8bd1cd2fcd2f
Tx public key: 8aa550d1040d8e4bfda11a66a54f541480d4fe148e186aec3de15f6f74f036d2
Timestamp: 1724593834 Timestamp [UCT]: 2024-08-25 13:50:34 Age [y:d:h:m:s]: 00:225:23:57:46
Block: 1095639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161382 RingCT/type: yes/0
Extra: 018aa550d1040d8e4bfda11a66a54f541480d4fe148e186aec3de15f6f74f036d2021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f72d21cd5fd123cf78704e728f4ddd509f174ee5d37170ea51587c5ec34acc79 0.600000000000 1570820 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": 1095649, "vin": [ { "gen": { "height": 1095639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f72d21cd5fd123cf78704e728f4ddd509f174ee5d37170ea51587c5ec34acc79" } } ], "extra": [ 1, 138, 165, 80, 209, 4, 13, 142, 75, 253, 161, 26, 102, 165, 79, 84, 20, 128, 212, 254, 20, 142, 24, 106, 236, 61, 225, 95, 111, 116, 240, 54, 210, 2, 17, 0, 0, 0, 2, 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