← previous blocknext block →recent activity
Analyzing
Block #106,958,798
20 transactions · 20 stateful · 2026-09-22 06:03:42 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,958,798 · 20 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
3w07w08w19w010w211w312w314w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d764242…46b0
0x34b655…2a6f
8 touches
6 conflicts
0xcd69374d…0ffa
0x34b655…2a6f
8 touches
6 conflicts
0x155e52ca…fac7
0x34b655…2a6f
6 touches
3 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0x9db7caf6…ccfc
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5e33d826…c389
0x34b655…2a6f
4 touches
1 conflict
0x63bc8147…dd42
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
6 conflicts on slot 0x7d764242f3…8146b0
Audit this contract →
← previous block·next block →recent activity