Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e432389830df9ebda605cf15783711cb43bdc9ed81ef9872ae3d2d0deec22a

Tx prefix hash: 588c2c5a78b9d53b58a004e2288721472b809f3126de57f3691413731574c023
Tx public key: b186ef0fdc2b74b08024528631d378634a5494ca3a5377cb12d56e6d159b167c
Timestamp: 1661934442 Timestamp [UCT]: 2022-08-31 08:27:22 Age [y:d:h:m:s]: 02:284:10:39:08
Block: 577647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724604 RingCT/type: yes/0
Extra: 01b186ef0fdc2b74b08024528631d378634a5494ca3a5377cb12d56e6d159b167c021100000002faf35c9c000000000000000000

1 output(s) for total of 7.481966995000 dcy

stealth address amount amount idx
00: d188299c9d03a2555fa66bf7f9a436fcdf92b7c3e154e6c0f789739eea5fb9e1 7.481966995000 1011041 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": 577657, "vin": [ { "gen": { "height": 577647 } } ], "vout": [ { "amount": 7481966995, "target": { "key": "d188299c9d03a2555fa66bf7f9a436fcdf92b7c3e154e6c0f789739eea5fb9e1" } } ], "extra": [ 1, 177, 134, 239, 15, 220, 43, 116, 176, 128, 36, 82, 134, 49, 211, 120, 99, 74, 84, 148, 202, 58, 83, 119, 203, 18, 213, 110, 109, 21, 155, 22, 124, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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