← previous blocknext block →recent activity
Analyzing
Block #94,792,441
17 transactions · 17 stateful · 2026-08-10 13:54:58 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,792,441 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w09w211w312w413w514w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4cc0421…c4de
0x34b655…2a6f
10 touches
10 conflicts
0xac8a5059…fd42
0x34b655…2a6f
10 touches
10 conflicts
0x40970e69…da50
0x2b46c0…1669
8 touches
6 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
8 touches
6 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
8 touches
6 conflicts
0xdb067026…9eb8
0x2b46c0…1669
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 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
10 conflicts on slot 0xc4cc04210b…f3c4de
Audit this contract →
← previous block·next block →recent activity