← previous blocknext block →recent activity
Analyzing
Block #94,850,754
13 transactions · 13 stateful · 2026-08-10 18:48:21 UTC
Parallelism
54/100
Blocked
38%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,850,754 · 13 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
2w03w15w26w37w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217dce8d…7e14
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0x2378c6e1…4dbd
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x8d3befc2…74a8
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
10 conflicts on slot 0x217dce8d30…647e14
Audit this contract →
← previous block·next block →recent activity