← previous blocknext block →recent activity
Analyzing
Block #92,434,431
14 transactions · 11 stateful · 2026-08-02 07:55:46 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,434,431 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w18w09w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9694185…1504
0x34b655…2a6f
4 touches
1 conflict
0x92339d95…0800
0xb1c8ea…8888
4 touches
1 conflict
0x5110a94f…86d1
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x69f1491a…1d4c
0x34b655…2a6f
3 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xb969418510…5b1504
Audit this contract →
← previous block·next block →recent activity