Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce9064502fac7e73dba8c92d5696d1beebfd4c99f81d8739d26842110ddcd8d

Tx prefix hash: 1b0911eaef3022996e7918b83876131791441deb454bd93f8243b066d89dd3e0
Tx public key: a0c80d0d3c1776801d67fed97217c9ef10591e4b2767f5a7ab02f3cf60c42994
Timestamp: 1582522137 Timestamp [UCT]: 2020-02-24 05:28:57 Age [y:d:h:m:s]: 04:223:22:03:08
Block: 71591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1052397 RingCT/type: yes/0
Extra: 01a0c80d0d3c1776801d67fed97217c9ef10591e4b2767f5a7ab02f3cf60c429940211000000010aca7173000000000000000000

1 output(s) for total of 355.459478597000 dcy

stealth address amount amount idx
00: e51801ecedf4a5dc01b4a3e66a7242855d57a76ba9b730df1dce09faa5f62f20 355.459478597000 132170 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": 71601, "vin": [ { "gen": { "height": 71591 } } ], "vout": [ { "amount": 355459478597, "target": { "key": "e51801ecedf4a5dc01b4a3e66a7242855d57a76ba9b730df1dce09faa5f62f20" } } ], "extra": [ 1, 160, 200, 13, 13, 60, 23, 118, 128, 29, 103, 254, 217, 114, 23, 201, 239, 16, 89, 30, 75, 39, 103, 245, 167, 171, 2, 243, 207, 96, 196, 41, 148, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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