Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63cb079e40931e16a87d3427f6554e50cf0046878d7880994ba6c72fb5100e89

Tx prefix hash: 5946f8e9b7aa35cbd164e89bcf1293ec4b2d27169f460213145766151af8a84b
Tx public key: f896accb4fcc954854d9a1bcce3d33ad9efb195a11cb6b497ab59c3af1d9c0c2
Timestamp: 1725168022 Timestamp [UCT]: 2024-09-01 05:20:22 Age [y:d:h:m:s]: 00:088:09:17:12
Block: 1100395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63225 RingCT/type: yes/0
Extra: 01f896accb4fcc954854d9a1bcce3d33ad9efb195a11cb6b497ab59c3af1d9c0c2021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97ae5f4b0bef49939af5e928163cd12577e0193366923f28233736503c952791 0.600000000000 1576374 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": 1100405, "vin": [ { "gen": { "height": 1100395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97ae5f4b0bef49939af5e928163cd12577e0193366923f28233736503c952791" } } ], "extra": [ 1, 248, 150, 172, 203, 79, 204, 149, 72, 84, 217, 161, 188, 206, 61, 51, 173, 158, 251, 25, 90, 17, 203, 107, 73, 122, 181, 156, 58, 241, 217, 192, 194, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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