← previous blocknext block →recent activity
Analyzing
Block #94,740,580
20 transactions · 20 stateful · 2026-08-10 09:33:10 UTC
Parallelism
60/100
Blocked
60%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,740,580 · 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
1w02w13w15w07w18w29w310w411w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b604e6…5152
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0x56b9250a…5093
0x34b655…2a6f
6 touches
4 conflicts
0x8e28932e…605f
0x34b655…2a6f
6 touches
3 conflicts
0xd4167a11…a19d
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 0xc6b604e60a…415152
Audit this contract →
← previous block·next block →recent activity