← previous blocknext block →recent activity
Analyzing
Block #106,109,706
16 transactions · 14 stateful · 2026-09-19 06:49:09 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,109,706 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w07w210w311w412w513w614w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x543f4651…59d0
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x159cff26…7665
0x34b655…2a6f
6 touches
3 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
6 touches
3 conflicts
0xfe4369ff…752e
0x34b655…2a6f
4 touches
1 conflict
0x3180cd66…aaef
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
10 conflicts on slot 0x543f4651ad…7259d0
Audit this contract →
← previous block·next block →recent activity