Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff433671f6fa42aab6ea35d41d7d96147529cb92ec32986ef01e65951a1479c6

Tx prefix hash: 3f95b4f8c35b20c141aac2688b5d0d84cc43e85d8180975b88a24258c067e3a9
Tx public key: 881f986990c1c98f4383d2b74309e43a2953695243b8dd125236764f85516ff0
Timestamp: 1737267497 Timestamp [UCT]: 2025-01-19 06:18:17 Age [y:d:h:m:s]: 00:149:18:39:39
Block: 1200519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106785 RingCT/type: yes/0
Extra: 01881f986990c1c98f4383d2b74309e43a2953695243b8dd125236764f85516ff0021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0dee2a4b12247ae9e76c8f6ce5fc45dacffc3a9ab3eb4d1f8e9b0581d09b84e 0.600000000000 1687164 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": 1200529, "vin": [ { "gen": { "height": 1200519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0dee2a4b12247ae9e76c8f6ce5fc45dacffc3a9ab3eb4d1f8e9b0581d09b84e" } } ], "extra": [ 1, 136, 31, 152, 105, 144, 193, 201, 143, 67, 131, 210, 183, 67, 9, 228, 58, 41, 83, 105, 82, 67, 184, 221, 18, 82, 54, 118, 79, 133, 81, 111, 240, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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