Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5d8f319b69155a0cead9a468b359b55bbe9151311ce97a4e8776e4cc152ff52

Tx prefix hash: f67a4dc0baad3274f51e063b902d188bc763ba98c196622c17b05c62595746e5
Tx public key: 4aa93b41d3d8ebffa56eb63dc176867ac16a06b2d0de26f5a934bbb14d0ceb07
Timestamp: 1709400430 Timestamp [UCT]: 2024-03-02 17:27:10 Age [y:d:h:m:s]: 01:035:11:12:55
Block: 969686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286337 RingCT/type: yes/0
Extra: 014aa93b41d3d8ebffa56eb63dc176867ac16a06b2d0de26f5a934bbb14d0ceb0702110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8f72c3962f9de01e8ca6748c1d53f6988d9ebfe435804d35dd3a42d5e3acdb4 0.600000000000 1429523 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": 969696, "vin": [ { "gen": { "height": 969686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8f72c3962f9de01e8ca6748c1d53f6988d9ebfe435804d35dd3a42d5e3acdb4" } } ], "extra": [ 1, 74, 169, 59, 65, 211, 216, 235, 255, 165, 110, 182, 61, 193, 118, 134, 122, 193, 106, 6, 178, 208, 222, 38, 245, 169, 52, 187, 177, 77, 12, 235, 7, 2, 17, 0, 0, 0, 6, 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