← previous blocknext block →recent activity
Analyzing
Block #94,470,790
17 transactions · 15 stateful · 2026-08-09 10:55:38 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,470,790 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w28w09w110w211w312w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x68c800ba…fc09
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2db
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2dc
0x34b655…2a6f
6 touches
3 conflicts
0x344f0672…7855
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
10 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity