Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff23ab970526a4d6591aca8b8e59a061cc116768c5f3217d64bdda6fae64b380

Tx prefix hash: cf1f1e364ecb08bd7df0e5d59dafad3fd33d9ec44bddb3606e6bc2657fe26ed4
Tx public key: dcac9679f13f98564eb2d0ef0cf4debc414f82dd12f493ea8cf6179313d2f42d
Timestamp: 1736733095 Timestamp [UCT]: 2025-01-13 01:51:35 Age [y:d:h:m:s]: 01:020:12:21:18
Block: 1196138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272967 RingCT/type: yes/0
Extra: 01dcac9679f13f98564eb2d0ef0cf4debc414f82dd12f493ea8cf6179313d2f42d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7dfed126560ff842735c7bbbddb7431914da1aa96a04c3fce331b791af933a8 0.600000000000 1682735 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": 1196148, "vin": [ { "gen": { "height": 1196138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7dfed126560ff842735c7bbbddb7431914da1aa96a04c3fce331b791af933a8" } } ], "extra": [ 1, 220, 172, 150, 121, 241, 63, 152, 86, 78, 178, 208, 239, 12, 244, 222, 188, 65, 79, 130, 221, 18, 244, 147, 234, 140, 246, 23, 147, 19, 210, 244, 45, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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