Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92b42e28291bb463ba12b0896372777c2d331421ef763b372e46649e8d0c4b57

Tx prefix hash: ac5aa8b0ed45047c79e049914a14f9801ab203fa32b4caaa59831cfaecb276ab
Tx public key: 115e91be703c8fd172ce00bf2a3a72942c2791db04d5485b7b60f9648db55f17
Timestamp: 1699806579 Timestamp [UCT]: 2023-11-12 16:29:39 Age [y:d:h:m:s]: 01:112:10:40:59
Block: 890150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341518 RingCT/type: yes/0
Extra: 01115e91be703c8fd172ce00bf2a3a72942c2791db04d5485b7b60f9648db55f1702110000000633af99f4000000000000000000

1 output(s) for total of 0.689546453000 dcy

stealth address amount amount idx
00: 2c6d3dc33ea93f1e2c8869027dc3c3e6113e5e55f56b2406edd7e2ec73df30be 0.689546453000 1346171 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": 890160, "vin": [ { "gen": { "height": 890150 } } ], "vout": [ { "amount": 689546453, "target": { "key": "2c6d3dc33ea93f1e2c8869027dc3c3e6113e5e55f56b2406edd7e2ec73df30be" } } ], "extra": [ 1, 17, 94, 145, 190, 112, 60, 143, 209, 114, 206, 0, 191, 42, 58, 114, 148, 44, 39, 145, 219, 4, 213, 72, 91, 123, 96, 249, 100, 141, 181, 95, 23, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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