Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef02efb3b135a3029c03464c4015ece77b4c9acdd26927f598974d6fa718f8b2

Tx prefix hash: f1a51f9c76d1588106b1f8fd8e491e23f923c727a54ce1dbfab7bb0cab802ebb
Tx public key: 9350303b21677128e508351567d7f04ce43717add0b2c924063ca77652936c24
Timestamp: 1696079179 Timestamp [UCT]: 2023-09-30 13:06:19 Age [y:d:h:m:s]: 02:083:01:33:25
Block: 859441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579056 RingCT/type: yes/0
Extra: 019350303b21677128e508351567d7f04ce43717add0b2c924063ca77652936c24021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.871596021000 dcy

stealth address amount amount idx
00: 83b656f1e7f16801bf64f9547f687fb5cb72bfeb45c68d7abf2c4af95b230d5c 0.871596021000 1313669 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": 859451, "vin": [ { "gen": { "height": 859441 } } ], "vout": [ { "amount": 871596021, "target": { "key": "83b656f1e7f16801bf64f9547f687fb5cb72bfeb45c68d7abf2c4af95b230d5c" } } ], "extra": [ 1, 147, 80, 48, 59, 33, 103, 113, 40, 229, 8, 53, 21, 103, 215, 240, 76, 228, 55, 23, 173, 208, 178, 201, 36, 6, 60, 167, 118, 82, 147, 108, 36, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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