← previous blocknext block →recent activity
Analyzing
Block #94,816,359
20 transactions · 20 stateful · 2026-08-10 15:55:18 UTC
Parallelism
60/100
Blocked
45%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,816,359 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w08w110w211w312w415w516w618w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6e6f436…ddc0
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
10 touches
10 conflicts
0xc17e8f36…5f58
0x34b655…2a6f
8 touches
6 conflicts
0xe44c4fc1…43b1
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xb825b472…1315
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
21 conflicts on slot 0xe6e6f4364f…80ddc0
Audit this contract →
← previous block·next block →recent activity