← previous blocknext block →recent activity
Analyzing
Block #106,921,942
18 transactions · 18 stateful · 2026-09-22 02:58:10 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,921,942 · 18 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
2w04w05w17w08w19w210w311w412w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0xa725b52a…4a88
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0xaa48aaa0…73fe
0x34b655…2a6f
4 touches
1 conflict
0xf7ed92bb…24eb
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity