Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8998a0260b1ca5d0e671e8fb1ada6c8e4cc934db61a8aa319c3d6c7f6286d5ef

Tx prefix hash: e689238bb0da033be70af198e9d06213c1edc3470c64e757d08d22d2db4d660f
Tx public key: febce82bc56a36f698e8f82ec3a8ef4c9a0f0141270c139e7d352557ea979bf1
Timestamp: 1608646173 Timestamp [UCT]: 2020-12-22 14:09:33 Age [y:d:h:m:s]: 04:073:00:19:50
Block: 167124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1064891 RingCT/type: yes/0
Extra: 01febce82bc56a36f698e8f82ec3a8ef4c9a0f0141270c139e7d352557ea979bf10211000006c14ea414e5000000000000000000

1 output(s) for total of 171.503107733000 dcy

stealth address amount amount idx
00: 7af2bb6f628c91048fbbec997de22b1e158e9d852b19e9defac5ee301b0917ca 171.503107733000 307533 of 0

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": 167134, "vin": [ { "gen": { "height": 167124 } } ], "vout": [ { "amount": 171503107733, "target": { "key": "7af2bb6f628c91048fbbec997de22b1e158e9d852b19e9defac5ee301b0917ca" } } ], "extra": [ 1, 254, 188, 232, 43, 197, 106, 54, 246, 152, 232, 248, 46, 195, 168, 239, 76, 154, 15, 1, 65, 39, 12, 19, 158, 125, 53, 37, 87, 234, 151, 155, 241, 2, 17, 0, 0, 6, 193, 78, 164, 20, 229, 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