Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c9dbf604a305ab9b4dbe6d04bd5f952e08f3e5453cf6186336352e7f805d3cc

Tx prefix hash: c84bc4193042f50c40b257fdc95e3b38ac4b77cfd85b63f9fd6d29f9fbaa30fe
Tx public key: f245fdf4d087190f51640639461489600a6c6eaf10c2b0fc47425b19d983ba85
Timestamp: 1708879306 Timestamp [UCT]: 2024-02-25 16:41:46 Age [y:d:h:m:s]: 01:111:17:16:17
Block: 965368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340794 RingCT/type: yes/0
Extra: 01f245fdf4d087190f51640639461489600a6c6eaf10c2b0fc47425b19d983ba850211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb1c6f1abb1dbfa71ae7be6dfa38525a01808e5b4c6c92b053d7b97e56a47938 0.600000000000 1425119 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": 965378, "vin": [ { "gen": { "height": 965368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb1c6f1abb1dbfa71ae7be6dfa38525a01808e5b4c6c92b053d7b97e56a47938" } } ], "extra": [ 1, 242, 69, 253, 244, 208, 135, 25, 15, 81, 100, 6, 57, 70, 20, 137, 96, 10, 108, 110, 175, 16, 194, 176, 252, 71, 66, 91, 25, 217, 131, 186, 133, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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