← previous blocknext block →recent activity
Analyzing
Block #94,686,472
21 transactions · 19 stateful · 2026-08-10 05:00:29 UTC
Parallelism
57/100
Blocked
47%
Avg conflicts / tx
1.19
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #94,686,472 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w39w412w513w616w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
12 touches
15 conflicts
0x3f798539…99c4
0x34b655…2a6f
8 touches
6 conflicts
0xa3e0aea5…5648
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0x390dd46c…deef
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2db
0x34b655…2a6f
6 touches
3 conflicts
0x90d127f4…5c92
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
15 conflicts on slot 0xcc351d6dd2…b1256b
Audit this contract →
← previous block·next block →recent activity