Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60f2dcb74b354cb819c9722ad4eaa34e2c27fa803715f5e2113beff0caf58046

Tx prefix hash: f954d26aca95d51c7913b631c303a3e4539ec91a1c9b272c9c955547833b1bd3
Tx public key: 82e97c04ce46a86c97f7c7740c14eeab93255054c0eaca83a35209c072f97173
Timestamp: 1715061038 Timestamp [UCT]: 2024-05-07 05:50:38 Age [y:d:h:m:s]: 00:137:08:17:18
Block: 1016619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98373 RingCT/type: yes/0
Extra: 0182e97c04ce46a86c97f7c7740c14eeab93255054c0eaca83a35209c072f9717302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad9fed1a84e3965944d3aeb2a485612bebc3c5cbc44ac8fcad965b13829225e9 0.600000000000 1480256 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": 1016629, "vin": [ { "gen": { "height": 1016619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad9fed1a84e3965944d3aeb2a485612bebc3c5cbc44ac8fcad965b13829225e9" } } ], "extra": [ 1, 130, 233, 124, 4, 206, 70, 168, 108, 151, 247, 199, 116, 12, 20, 238, 171, 147, 37, 80, 84, 192, 234, 202, 131, 163, 82, 9, 192, 114, 249, 113, 115, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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