Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1122534d8f93705834e55caf1fbe8a50930943cf88fa9c44b32cea5d264eb8bc

Tx prefix hash: aae7a844ce32041c50fecfe34743a5cd74763c5b594208a20c1371d9b48669f0
Tx public key: 9ec8d296d7fd968b7e945e3f221de68ee49711b8356b5d7d4393119e5124fe3d
Timestamp: 1721044766 Timestamp [UCT]: 2024-07-15 11:59:26 Age [y:d:h:m:s]: 00:260:02:24:23
Block: 1066235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185793 RingCT/type: yes/0
Extra: 019ec8d296d7fd968b7e945e3f221de68ee49711b8356b5d7d4393119e5124fe3d02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b8761e2c6381f9a12023d0cec5478176250b3f2c80da8ecc1e73a6ab8d04df5 0.600000000000 1536808 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": 1066245, "vin": [ { "gen": { "height": 1066235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b8761e2c6381f9a12023d0cec5478176250b3f2c80da8ecc1e73a6ab8d04df5" } } ], "extra": [ 1, 158, 200, 210, 150, 215, 253, 150, 139, 126, 148, 94, 63, 34, 29, 230, 142, 228, 151, 17, 184, 53, 107, 93, 125, 67, 147, 17, 158, 81, 36, 254, 61, 2, 17, 0, 0, 0, 10, 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