Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79aa989b2f81ae569887211dbc3306f662dbd1eafc4ed7fc556ddda1c242f110

Tx prefix hash: 50492755d8e8a17f209ecc4c29ffb89cf2ba998c434342142b8150d2b93a9b30
Tx public key: 8b74fb5bc5dae54eb90f4c83eeb22c6eb55c978553cbced2b56f6139ef8bda8a
Timestamp: 1710903283 Timestamp [UCT]: 2024-03-20 02:54:43 Age [y:d:h:m:s]: 01:028:16:28:11
Block: 982158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281458 RingCT/type: yes/0
Extra: 018b74fb5bc5dae54eb90f4c83eeb22c6eb55c978553cbced2b56f6139ef8bda8a02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d60703759e2fd3ba38648d0d3ea2e612ded78446719931ef174ef8af26b897da 0.600000000000 1442263 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": 982168, "vin": [ { "gen": { "height": 982158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d60703759e2fd3ba38648d0d3ea2e612ded78446719931ef174ef8af26b897da" } } ], "extra": [ 1, 139, 116, 251, 91, 197, 218, 229, 78, 185, 15, 76, 131, 238, 178, 44, 110, 181, 92, 151, 133, 83, 203, 206, 210, 181, 111, 97, 57, 239, 139, 218, 138, 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