← previous blocknext block →recent activity
Analyzing
Block #94,696,129
26 transactions · 20 stateful · 2026-08-10 05:49:03 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
1.38
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #94,696,129 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w18w29w310w411w512w616w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x20b90997…cf6b
0x34b655…2a6f
12 touches
15 conflicts
0xa3f095f5…bd87
0x34b655…2a6f
12 touches
15 conflicts
0xd79c9727…1233
0x34b655…2a6f
8 touches
6 conflicts
0xa351b7d0…8a20
0x34b655…2a6f
8 touches
6 conflicts
0x72c8aeb2…9921
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity