← previous blocknext block →recent activity
Analyzing
Block #94,810,957
12 transactions · 12 stateful · 2026-08-10 15:28:07 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,810,957 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x30934885…333a
0xd32edf…ff58
3 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x21ef0807…d889
0x34b655…2a6f
2 touches
0 conflicts
0x28c180e1…f1e2
0x34b655…2a6f
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity