Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec888b8f5b4167d2bb662833ba18c86f8a366e1451ea14e8b02481a242cf9438

Tx prefix hash: 48f99d5e9ed56ba669685402426d51389ec4a58557603a04966815d7e866f76a
Tx public key: 7daae8e39b87cb644a2a5090d912b797267e5bc1357abac8dfbb3b7ce575b56a
Timestamp: 1634860796 Timestamp [UCT]: 2021-10-21 23:59:56 Age [y:d:h:m:s]: 03:066:18:07:25
Block: 357726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 826022 RingCT/type: yes/0
Extra: 017daae8e39b87cb644a2a5090d912b797267e5bc1357abac8dfbb3b7ce575b56a0211000000043fad1932000000000000000000

1 output(s) for total of 40.059513907000 dcy

stealth address amount amount idx
00: 86ec9d3b5e82c8b582e0157d9c4e7e2e00c444563b3ebec585e3dad4c09d986a 40.059513907000 729316 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": 357736, "vin": [ { "gen": { "height": 357726 } } ], "vout": [ { "amount": 40059513907, "target": { "key": "86ec9d3b5e82c8b582e0157d9c4e7e2e00c444563b3ebec585e3dad4c09d986a" } } ], "extra": [ 1, 125, 170, 232, 227, 155, 135, 203, 100, 74, 42, 80, 144, 217, 18, 183, 151, 38, 126, 91, 193, 53, 122, 186, 200, 223, 187, 59, 124, 229, 117, 181, 106, 2, 17, 0, 0, 0, 4, 63, 173, 25, 50, 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