Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b60f2284ad17f8d2cf13549539d961b6cbff747944b2bf4bae6c2379cc313d60

Tx prefix hash: 790c92b6df291d4d4d317c5589598044e2aeff335f0d543635b21cdf8e85a6a4
Tx public key: e63322b97f9d04fcbb186685725beda7f933cddc4cd965b7fd5ebe41d2d2c066
Timestamp: 1717177773 Timestamp [UCT]: 2024-05-31 17:49:33 Age [y:d:h:m:s]: 00:298:19:57:00
Block: 1034160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213561 RingCT/type: yes/0
Extra: 01e63322b97f9d04fcbb186685725beda7f933cddc4cd965b7fd5ebe41d2d2c0660211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08b5896e9b01d005ff1afd57bc4d6dbbf083dce78ca243d96b85107ddc035d1d 0.600000000000 1502643 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": 1034170, "vin": [ { "gen": { "height": 1034160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b5896e9b01d005ff1afd57bc4d6dbbf083dce78ca243d96b85107ddc035d1d" } } ], "extra": [ 1, 230, 51, 34, 185, 127, 157, 4, 252, 187, 24, 102, 133, 114, 91, 237, 167, 249, 51, 205, 220, 76, 217, 101, 183, 253, 94, 190, 65, 210, 210, 192, 102, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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