Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3107c1d2ac4dd9a2efa94bade15844c0a0c72f212c52181a07701d10f11533be

Tx prefix hash: 3b6b18a2aae0c19d9c38637a16a129bfc5d0cd0e19673d11e70efc4f3b0e70dc
Tx public key: 87c65546edab36d32e027aca4970865571f238a6bec0cf849cece1adb4acefd2
Timestamp: 1699630179 Timestamp [UCT]: 2023-11-10 15:29:39 Age [y:d:h:m:s]: 01:140:03:12:06
Block: 888687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361332 RingCT/type: yes/0
Extra: 0187c65546edab36d32e027aca4970865571f238a6bec0cf849cece1adb4acefd2021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.697286180000 dcy

stealth address amount amount idx
00: e1210a431cc14b15502b272e66be218f65e84476a161a1e56e710722fa718325 0.697286180000 1344642 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": 888697, "vin": [ { "gen": { "height": 888687 } } ], "vout": [ { "amount": 697286180, "target": { "key": "e1210a431cc14b15502b272e66be218f65e84476a161a1e56e710722fa718325" } } ], "extra": [ 1, 135, 198, 85, 70, 237, 171, 54, 211, 46, 2, 122, 202, 73, 112, 134, 85, 113, 242, 56, 166, 190, 192, 207, 132, 156, 236, 225, 173, 180, 172, 239, 210, 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