Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95e938b9c0ea73981eb90fb0b11cbe7bbcd1ea3be2b77af890f3730474f1136e

Tx prefix hash: e2c08008288b7303bfece49afbfdad823f6b35b251bdc7115cbec9e4466fe212
Tx public key: 906e5dad6e992c2108ec63d9e19c488d7291a51a2cb4fd972bc1c7cb33536080
Timestamp: 1733209030 Timestamp [UCT]: 2024-12-03 06:57:10 Age [y:d:h:m:s]: 00:341:21:15:03
Block: 1166958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241876 RingCT/type: yes/0
Extra: 01906e5dad6e992c2108ec63d9e19c488d7291a51a2cb4fd972bc1c7cb33536080021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ec3da082ace10205442e04345dd306830260e4833e79ed739f5a2600aa0dfa6 0.600000000000 1652651 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": 1166968, "vin": [ { "gen": { "height": 1166958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ec3da082ace10205442e04345dd306830260e4833e79ed739f5a2600aa0dfa6" } } ], "extra": [ 1, 144, 110, 93, 173, 110, 153, 44, 33, 8, 236, 99, 217, 225, 156, 72, 141, 114, 145, 165, 26, 44, 180, 253, 151, 43, 193, 199, 203, 51, 83, 96, 128, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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