← previous blocknext block →recent activity
Analyzing
Block #94,482,603
17 transactions · 17 stateful · 2026-08-09 11:55:06 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,482,603 · 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
3w04w15w26w37w49w010w112w213w514w316w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x156552f7…c066
0x34b655…2a6f
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa6389d47…9a28
0x34b655…2a6f
6 touches
3 conflicts
0x114041dc…f5c8
0x065c9d…c394
5 touches
3 conflicts
0x3522af60…d679
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6571
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
3 conflicts on slot 0x156552f70b…11c066
Audit this contract →
← previous block·next block →recent activity