← previous blocknext block →recent activity
Analyzing
Block #106,551,620
23 transactions · 23 stateful · 2026-09-20 19:53:18 UTC
Parallelism
52/100
Blocked
57%
Avg conflicts / tx
2.57
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,551,620 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w18w210w311w412w513w614w715w816w917w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd193364c…cd91
0x34b655…2a6f
22 touches
55 conflicts
0xc1da8f73…484c
0x34b655…2a6f
10 touches
10 conflicts
0x69411fb3…e36d
0x34b655…2a6f
8 touches
6 conflicts
0xe530b2cf…6f95
0x34b655…2a6f
8 touches
6 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0x8f5a38d8…c230
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
55 conflicts on slot 0xd193364c86…7ecd91
Audit this contract →
← previous block·next block →recent activity