Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6a8f7f12af3f57f73958a39c53bb8f3d51f56a9865008843c755efc07d0779

Tx prefix hash: c829818ec77a3d037877364c34214342abe0170d18214230f031c1bf1f69de85
Tx public key: c3010daec7bf18e8e92b2a0b4ac5973c6b64e1f5a19f6c94e71e50daef62a2a5
Timestamp: 1575993451 Timestamp [UCT]: 2019-12-10 15:57:31 Age [y:d:h:m:s]: 05:062:04:58:08
Block: 24923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190119 RingCT/type: yes/0
Extra: 01c3010daec7bf18e8e92b2a0b4ac5973c6b64e1f5a19f6c94e71e50daef62a2a5021100000009ad433a0b000000000000000000

1 output(s) for total of 507.481978885000 dcy

stealth address amount amount idx
00: f9392975a8128a7bab88c6f652a3adc5a36dcb326e4e16104d8df2180a6aa8e3 507.481978885000 40946 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": 24933, "vin": [ { "gen": { "height": 24923 } } ], "vout": [ { "amount": 507481978885, "target": { "key": "f9392975a8128a7bab88c6f652a3adc5a36dcb326e4e16104d8df2180a6aa8e3" } } ], "extra": [ 1, 195, 1, 13, 174, 199, 191, 24, 232, 233, 43, 42, 11, 74, 197, 151, 60, 107, 100, 225, 245, 161, 159, 108, 148, 231, 30, 80, 218, 239, 98, 162, 165, 2, 17, 0, 0, 0, 9, 173, 67, 58, 11, 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