Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 142c5da6f203e321f801bca0a534bf77e6124eee8aba685e4bebc092ff62f074

Tx prefix hash: d416cfb93ce9137c04b9a10ae957b147e6c051498ffee35d12c41d161554415a
Tx public key: a8ce4afb318bb97e134e9fb55122039e856d0b65bd2ad271e5ea87788f1f7ade
Timestamp: 1721024425 Timestamp [UCT]: 2024-07-15 06:20:25 Age [y:d:h:m:s]: 00:242:18:35:14
Block: 1066060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173436 RingCT/type: yes/0
Extra: 01a8ce4afb318bb97e134e9fb55122039e856d0b65bd2ad271e5ea87788f1f7ade021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82ec788295520dfc3db2b6b7c2ab3bb0f5e056ee9707174e66fecc346c26123c 0.600000000000 1536631 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": 1066070, "vin": [ { "gen": { "height": 1066060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82ec788295520dfc3db2b6b7c2ab3bb0f5e056ee9707174e66fecc346c26123c" } } ], "extra": [ 1, 168, 206, 74, 251, 49, 139, 185, 126, 19, 78, 159, 181, 81, 34, 3, 158, 133, 109, 11, 101, 189, 42, 210, 113, 229, 234, 135, 120, 143, 31, 122, 222, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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