Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82fc3091899e6e931898fc3af477969ae2d0ffd3052750594ae4913b650aa03c

Tx prefix hash: ecfd2cf26f9a881dcd42a14ff06e723d373d823289fbfd3befdb76181e9ed3f8
Tx public key: 7a6f2be9a2b8d88854cf5524ba201e29d1aa71d297ed848b679073c9273526bd
Timestamp: 1703265981 Timestamp [UCT]: 2023-12-22 17:26:21 Age [y:d:h:m:s]: 01:176:01:29:22
Block: 918822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386904 RingCT/type: yes/0
Extra: 017a6f2be9a2b8d88854cf5524ba201e29d1aa71d297ed848b679073c9273526bd02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1bb45e85856d8664b7b69a773b2a0cd5d17bb9cf6e58d5b9139b292f50b31c3 0.600000000000 1376486 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": 918832, "vin": [ { "gen": { "height": 918822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1bb45e85856d8664b7b69a773b2a0cd5d17bb9cf6e58d5b9139b292f50b31c3" } } ], "extra": [ 1, 122, 111, 43, 233, 162, 184, 216, 136, 84, 207, 85, 36, 186, 32, 30, 41, 209, 170, 113, 210, 151, 237, 132, 139, 103, 144, 115, 201, 39, 53, 38, 189, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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