Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5c38a6ef30753bc7f42dc7d2af72643a722f2edb74b3e2643db2ff441d2fb06

Tx prefix hash: a0fd9e6eda7f5546885e7df0cd3ba45ac3668d0df1dfdc6a760d5f8ebfe53f89
Tx public key: 01a6a26dae554a8a4a1b2b6a080e4ec61ac3bddcc46fef3a0ed2eb85efa595d6
Timestamp: 1707675330 Timestamp [UCT]: 2024-02-11 18:15:30 Age [y:d:h:m:s]: 01:130:06:58:59
Block: 955371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354052 RingCT/type: yes/0
Extra: 0101a6a26dae554a8a4a1b2b6a080e4ec61ac3bddcc46fef3a0ed2eb85efa595d60211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e8222e878a5d71b53b4732d7242fdaf7c89bd0c668d0073020bf0f17aec34d7 0.600000000000 1414659 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": 955381, "vin": [ { "gen": { "height": 955371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e8222e878a5d71b53b4732d7242fdaf7c89bd0c668d0073020bf0f17aec34d7" } } ], "extra": [ 1, 1, 166, 162, 109, 174, 85, 74, 138, 74, 27, 43, 106, 8, 14, 78, 198, 26, 195, 189, 220, 196, 111, 239, 58, 14, 210, 235, 133, 239, 165, 149, 214, 2, 17, 0, 0, 0, 5, 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