Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dafd3975aafc1f65ad07c16fd088600d14bf9c41d495dce263465d94e80c372

Tx prefix hash: c866f12b2b6277aa1be5062f93528482e6108bdad6d274f7bebc43725d5ff6b0
Tx public key: b5356a7cd387a3c5e708c0a8641f9257fddcb27544b31470104cddd10c18dc71
Timestamp: 1707287369 Timestamp [UCT]: 2024-02-07 06:29:29 Age [y:d:h:m:s]: 01:021:00:20:29
Block: 952154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276032 RingCT/type: yes/0
Extra: 01b5356a7cd387a3c5e708c0a8641f9257fddcb27544b31470104cddd10c18dc7102110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aefa8c6b9f722167c067f754ba91c1535fff186c4aa584d1ec43020acd1c9ac 0.600000000000 1411034 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": 952164, "vin": [ { "gen": { "height": 952154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aefa8c6b9f722167c067f754ba91c1535fff186c4aa584d1ec43020acd1c9ac" } } ], "extra": [ 1, 181, 53, 106, 124, 211, 135, 163, 197, 231, 8, 192, 168, 100, 31, 146, 87, 253, 220, 178, 117, 68, 179, 20, 112, 16, 76, 221, 209, 12, 24, 220, 113, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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