← previous blocknext block →recent activity
Analyzing
Block #106,408,009
17 transactions · 10 stateful · 2026-09-20 07:50:28 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,408,009 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w010w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf537d3a9…730b
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xaa188d6b…3d5c
0x34b655…2a6f
3 touches
1 conflict
0x02fa927d…6468
0x34b655…2a6f
2 touches
0 conflicts
0x573e497e…dab5
0x34b655…2a6f
2 touches
0 conflicts
0x9b255f29…885c
0x34b655…2a6f
2 touches
0 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity