Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80e08a0d138921edbaea6eba9c78a145a7ec3a300625de0712597ce6c41db4d3

Tx prefix hash: bb446d71b803988c86bb0197ab8fc825c8901abcad3f2efd8b34203361ec08dc
Tx public key: 7a00cf6a010dc44814ac4b82e24fd3e33ca3482c49865a3a12cfa095768dc5d7
Timestamp: 1682098500 Timestamp [UCT]: 2023-04-21 17:35:00 Age [y:d:h:m:s]: 02:171:17:34:29
Block: 743579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 642537 RingCT/type: yes/0
Extra: 017a00cf6a010dc44814ac4b82e24fd3e33ca3482c49865a3a12cfa095768dc5d7021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.109668951000 dcy

stealth address amount amount idx
00: 09d6d2c8e29bbfb3351703aab0f6eb3b5bad291654f260c4adcc17868d641208 2.109668951000 1190770 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": 743589, "vin": [ { "gen": { "height": 743579 } } ], "vout": [ { "amount": 2109668951, "target": { "key": "09d6d2c8e29bbfb3351703aab0f6eb3b5bad291654f260c4adcc17868d641208" } } ], "extra": [ 1, 122, 0, 207, 106, 1, 13, 196, 72, 20, 172, 75, 130, 226, 79, 211, 227, 60, 163, 72, 44, 73, 134, 90, 58, 18, 207, 160, 149, 118, 141, 197, 215, 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