Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e05bcb95220767609d1f30196dadb658f9dd448d9fdb4704cfeee779b8e282f0

Tx prefix hash: 5527c0a0206a18a871f3b28f7e23d050cc03de35376cec0fbb95fd6023cc5638
Tx public key: 0abd635b8b6d13071d1e6b3d93405501c91e6060252ec8a5ce89aa7a09e74514
Timestamp: 1732843493 Timestamp [UCT]: 2024-11-29 01:24:53 Age [y:d:h:m:s]: 00:103:16:56:00
Block: 1163932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73929 RingCT/type: yes/0
Extra: 010abd635b8b6d13071d1e6b3d93405501c91e6060252ec8a5ce89aa7a09e745140211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90f934b74f0da957320d0f6f6cbd1741275e611d0c99cee02af1de69d15bcb3d 0.600000000000 1649603 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": 1163942, "vin": [ { "gen": { "height": 1163932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90f934b74f0da957320d0f6f6cbd1741275e611d0c99cee02af1de69d15bcb3d" } } ], "extra": [ 1, 10, 189, 99, 91, 139, 109, 19, 7, 29, 30, 107, 61, 147, 64, 85, 1, 201, 30, 96, 96, 37, 46, 200, 165, 206, 137, 170, 122, 9, 231, 69, 20, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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