← previous blocknext block →recent activity
Analyzing
Block #94,807,729
14 transactions · 11 stateful · 2026-08-10 15:11:52 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,807,729 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x5ab7afd1…18a8
0x1efe02…37d6
2 touches
0 conflicts
0x6e096e52…7eb5
0x1efe02…37d6
2 touches
0 conflicts
0xd0cd5b3b…613d
0x1efe02…37d6
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 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
1 conflict on slot 0xf2f4727df6…a5cdb7
Audit this contract →
← previous block·next block →recent activity