← previous blocknext block →recent activity
Analyzing
Block #94,278,349
13 transactions · 13 stateful · 2026-08-08 18:38:16 UTC
Parallelism
39/100
Blocked
62%
Avg conflicts / tx
2.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,278,349 · 13 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
1w02w13w24w35w46w47w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3383813…4a0c
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x4069c511…21c8
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xd79c9727…1233
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xd8e3e694…f0c8
0x34b655…2a6f
6 touches
5 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
21 conflicts on slot 0xf338381336…ec4a0c
Audit this contract →
← previous block·next block →recent activity