← previous blocknext block →recent activity
Analyzing
Block #93,846,464
15 transactions · 14 stateful · 2026-08-07 06:19:20 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.8
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,846,464 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w17w29w211w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6636a104…d595
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2db
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2dc
0x34b655…2a6f
6 touches
3 conflicts
0x687a4940…fce9
0x34b655…2a6f
6 touches
3 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 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 0x6636a1041f…2dd595
Audit this contract →
← previous block·next block →recent activity