Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffb65c40134fca41125c14687dc3cf2f9cdf4f906cf7ec18ed333290446e5a6f

Tx prefix hash: 2254129a10390c977dc29216735979d39fe1ae46047a36254f0b835e7a02e18d
Tx public key: 1593401cf8f4e513c87a35325cace456893a246f1374c6f33157bee465d19a40
Timestamp: 1699262345 Timestamp [UCT]: 2023-11-06 09:19:05 Age [y:d:h:m:s]: 01:110:10:00:29
Block: 885632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340069 RingCT/type: yes/0
Extra: 011593401cf8f4e513c87a35325cace456893a246f1374c6f33157bee465d19a4002110000000275e3f0e9000000000000000000

1 output(s) for total of 0.713729332000 dcy

stealth address amount amount idx
00: b50a066898bba41c6daf6e07c6b5393d2df047f7d0fd09a63d4f4c97ddabb3b8 0.713729332000 1341413 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": 885642, "vin": [ { "gen": { "height": 885632 } } ], "vout": [ { "amount": 713729332, "target": { "key": "b50a066898bba41c6daf6e07c6b5393d2df047f7d0fd09a63d4f4c97ddabb3b8" } } ], "extra": [ 1, 21, 147, 64, 28, 248, 244, 229, 19, 200, 122, 53, 50, 92, 172, 228, 86, 137, 58, 36, 111, 19, 116, 198, 243, 49, 87, 190, 228, 101, 209, 154, 64, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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