← previous blocknext block →recent activity
Analyzing
Block #95,626,109
20 transactions · 18 stateful · 2026-08-13 12:02:38 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,626,109 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w09w111w212w313w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xea674754…0e82
0x34b655…2a6f
8 touches
6 conflicts
0x4af8f8d2…0850
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x53bda555…3810
0x34b655…2a6f
4 touches
1 conflict
0x5e78c401…7a7e
0x34b655…2a6f
4 touches
1 conflict
0x7523c6af…ea66
0x34b655…2a6f
4 touches
1 conflict
0x79a6b7b8…f1b1
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity