Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b066be1e05bd5a100c8c53481e32ea2abb0db746dfd53572e5dd1caf9f6041e

Tx prefix hash: 81e1fd8a8a94ac0fd4d10e2a34a2a5e72f9cd813245cb050ec8896c845706f0e
Tx public key: 7b2bf08489f308ba25ac1b865051af892509fc02e0a9d9e17d94b05089a22bb8
Timestamp: 1634951457 Timestamp [UCT]: 2021-10-23 01:10:57 Age [y:d:h:m:s]: 04:009:12:44:33
Block: 358479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043493 RingCT/type: yes/0
Extra: 017b2bf08489f308ba25ac1b865051af892509fc02e0a9d9e17d94b05089a22bb80211000000025410958b000000000000000000

1 output(s) for total of 39.830033571000 dcy

stealth address amount amount idx
00: 58127cba6f4844b2c31dc4c795d14d86c7d85fe67f82c7c9b90c33ca9b3b3195 39.830033571000 730426 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": 358489, "vin": [ { "gen": { "height": 358479 } } ], "vout": [ { "amount": 39830033571, "target": { "key": "58127cba6f4844b2c31dc4c795d14d86c7d85fe67f82c7c9b90c33ca9b3b3195" } } ], "extra": [ 1, 123, 43, 240, 132, 137, 243, 8, 186, 37, 172, 27, 134, 80, 81, 175, 137, 37, 9, 252, 2, 224, 169, 217, 225, 125, 148, 176, 80, 137, 162, 43, 184, 2, 17, 0, 0, 0, 2, 84, 16, 149, 139, 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