← previous blocknext block →recent activity
Analyzing
Block #94,750,189
35 transactions · 27 stateful · 2026-08-10 10:22:06 UTC
Parallelism
80/100
Blocked
70%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,750,189 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w38w310w411w512w614w417w427w428w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00ddbbf2…4588
0x34b655…2a6f
10 touches
10 conflicts
0x537badca…2d3d
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0002
0xeae24c…0be0
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
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
10 conflicts on slot 0x00ddbbf292…ff4588
Audit this contract →
← previous block·next block →recent activity