Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79244e8e04c8aa01d9e4be4ce8da3093e2c55416b67c20992217cbc27360693e

Tx prefix hash: 30169dfdf882112f4ba31f96b08d26683b6894af6983881d7186cc3f20c2249f
Tx public key: 26c60cd4d31a69a62dbe876c6a84068315fc4cbaa5aabc55dd78ab494b0a8843
Timestamp: 1733521180 Timestamp [UCT]: 2024-12-06 21:39:40 Age [y:d:h:m:s]: 00:112:07:59:38
Block: 1169547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80079 RingCT/type: yes/0
Extra: 0126c60cd4d31a69a62dbe876c6a84068315fc4cbaa5aabc55dd78ab494b0a8843021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7e0aed4cbb4715c2b72f910ba0d08861b75fd72c8b010aa50eca76a8ac9c5fe 0.600000000000 1655266 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": 1169557, "vin": [ { "gen": { "height": 1169547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7e0aed4cbb4715c2b72f910ba0d08861b75fd72c8b010aa50eca76a8ac9c5fe" } } ], "extra": [ 1, 38, 198, 12, 212, 211, 26, 105, 166, 45, 190, 135, 108, 106, 132, 6, 131, 21, 252, 76, 186, 165, 170, 188, 85, 221, 120, 171, 73, 75, 10, 136, 67, 2, 17, 0, 0, 0, 4, 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