← previous blocknext block →recent activity
Analyzing
Block #106,957,190
30 transactions · 29 stateful · 2026-09-22 05:55:36 UTC
Parallelism
87/100
Blocked
34%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,957,190 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w111w012w113w116w218w319w221w123w324w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ddef8d6…636b
0x34b655…2a6f
8 touches
6 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x743f0e02…73ec
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0x858e40c0…7e30
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x7ddef8d6ee…8d636b
Audit this contract →
← previous block·next block →recent activity