← previous blocknext block →recent activity
Analyzing
Block #106,385,576
30 transactions · 29 stateful · 2026-09-20 05:57:35 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,385,576 · 30 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
3w08w110w213w220w221w322w423w524w628w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2507c7b7…58f7
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
0x553a79c0…790c
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
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
15 conflicts on slot 0x2507c7b76a…8058f7
Audit this contract →
← previous block·next block →recent activity