Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c98fcbf2aa8de6a2e2ade4870724d6e80fccf00c20dde99df26b79a11cf1ff1e

Tx prefix hash: 7fe97359e53cdc4121dcef4bd85824b32f2019cfe50422dc6a875091a72c82fb
Tx public key: ac27b688a12c7042de2dc740f1237a7d0460f8c0cc97a25d0533650df940910f
Timestamp: 1726213278 Timestamp [UCT]: 2024-09-13 07:41:18 Age [y:d:h:m:s]: 00:203:14:23:26
Block: 1109060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145344 RingCT/type: yes/0
Extra: 01ac27b688a12c7042de2dc740f1237a7d0460f8c0cc97a25d0533650df940910f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 026f81a9f6032901230b4a2c19d2dc5145b6f4c54a61dae5fd148586dc8790e8 0.600000000000 1587177 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": 1109070, "vin": [ { "gen": { "height": 1109060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "026f81a9f6032901230b4a2c19d2dc5145b6f4c54a61dae5fd148586dc8790e8" } } ], "extra": [ 1, 172, 39, 182, 136, 161, 44, 112, 66, 222, 45, 199, 64, 241, 35, 122, 125, 4, 96, 248, 192, 204, 151, 162, 93, 5, 51, 101, 13, 249, 64, 145, 15, 2, 17, 0, 0, 0, 2, 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