Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a8646c56089a727085b9a815aba0d27db004cfc8ea5d9633363416b0aefcc8

Tx prefix hash: 096a7499b9d2fcf4e54b8690a2e621d885608083dba0f562d4ad02fd38f90b80
Tx public key: 039d75e069be90e76ab633087fceaf6eaf5c9d89261affe27bf739426a11d1a6
Timestamp: 1718809581 Timestamp [UCT]: 2024-06-19 15:06:21 Age [y:d:h:m:s]: 01:147:17:44:09
Block: 1047691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364149 RingCT/type: yes/0
Extra: 01039d75e069be90e76ab633087fceaf6eaf5c9d89261affe27bf739426a11d1a602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52c57537f2b3d62c006b61d9396f7c3ed01dc3f339f2ee371b54e308cecc40f9 0.600000000000 1517578 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": 1047701, "vin": [ { "gen": { "height": 1047691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52c57537f2b3d62c006b61d9396f7c3ed01dc3f339f2ee371b54e308cecc40f9" } } ], "extra": [ 1, 3, 157, 117, 224, 105, 190, 144, 231, 106, 182, 51, 8, 127, 206, 175, 110, 175, 92, 157, 137, 38, 26, 255, 226, 123, 247, 57, 66, 106, 17, 209, 166, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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