← previous blocknext block →recent activity
Analyzing
Block #106,917,343
33 transactions · 33 stateful · 2026-09-22 02:35:02 UTC
Parallelism
48/100
Blocked
70%
Avg conflicts / tx
2.94
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,917,343 · 33 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w17w08w19w210w311w412w513w614w715w816w117w926w1030w232w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea79e6d3…68ad
0x34b655…2a6f
20 touches
45 conflicts
0x4db105b4…056c
0x34b655…2a6f
18 touches
36 conflicts
0x42522e76…2592
0x34b655…2a6f
18 touches
36 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
18 touches
36 conflicts
0x81d2de5b…f95e
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0x05ae81ac…b6d2
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 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
45 conflicts on slot 0xea79e6d350…ec68ad
Audit this contract →
← previous block·next block →recent activity