← previous blocknext block →recent activity
Analyzing
Block #94,486,769
21 transactions · 16 stateful · 2026-08-09 12:16:03 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,486,769 · 21 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
1w02w16w07w18w29w310w418w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1911dfb0…a94d
0x34b655…2a6f
6 touches
3 conflicts
0x2b75d304…d186
0x34b655…2a6f
4 touches
1 conflict
0x2bc437df…a6c7
0x34b655…2a6f
4 touches
1 conflict
0x3e47abc3…6968
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6819f434…82c8
0x34b655…2a6f
4 touches
1 conflict
0x6819f434…82c9
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity