← previous blocknext block →recent activity
Analyzing
Block #106,453,931
27 transactions · 24 stateful · 2026-09-20 11:41:39 UTC
Parallelism
48/100
Blocked
75%
Avg conflicts / tx
2.56
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,453,931 · 27 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w27w19w111w012w313w414w315w517w518w619w720w821w922w1023w1124w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31e47e6c…87f9
0x34b655…2a6f
16 touches
28 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
16 touches
28 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
14 touches
21 conflicts
0xc3baa205…f26e
0x34b655…2a6f
10 touches
10 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
10 touches
10 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0xc0a692d1…0ef8
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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
28 conflicts on slot 0x31e47e6c3b…7387f9
Audit this contract →
← previous block·next block →recent activity