← previous blocknext block →recent activity
Analyzing
Block #106,575,832
23 transactions · 20 stateful · 2026-09-20 21:55:09 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,575,832 · 23 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
1w02w18w012w016w117w219w320w421w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x471f9f88…c6c8
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdb95e18e…c73d
0x1b6862…e19c
4 touches
1 conflict
0x3769d608…be6d
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 0x471f9f880b…8bc6c8
Audit this contract →
← previous block·next block →recent activity