Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a1e960ad629c23410ba46860ae5c207033564d0f596716efe11119d12428a6d

Tx prefix hash: be99180a13568de80fe4b286060a289f913d0bcab0fc876f11f6562af0a0be91
Tx public key: 8716bff4f4e54395c61cb12d029fbe680900328d874a23d81db4740963c068fd
Timestamp: 1675046885 Timestamp [UCT]: 2023-01-30 02:48:05 Age [y:d:h:m:s]: 01:348:02:42:34
Block: 685764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509763 RingCT/type: yes/0
Extra: 018716bff4f4e54395c61cb12d029fbe680900328d874a23d81db4740963c068fd021100000002835e4d22000000000000000000

1 output(s) for total of 3.279284739000 dcy

stealth address amount amount idx
00: 28b8d31a6b0ac9a77ac989ed2330c2e2adee718457d9a26f2b922db9d2fbd284 3.279284739000 1128145 of 0

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": 685774, "vin": [ { "gen": { "height": 685764 } } ], "vout": [ { "amount": 3279284739, "target": { "key": "28b8d31a6b0ac9a77ac989ed2330c2e2adee718457d9a26f2b922db9d2fbd284" } } ], "extra": [ 1, 135, 22, 191, 244, 244, 229, 67, 149, 198, 28, 177, 45, 2, 159, 190, 104, 9, 0, 50, 141, 135, 74, 35, 216, 29, 180, 116, 9, 99, 192, 104, 253, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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