← previous blocknext block →recent activity
Analyzing
Block #106,548,649
22 transactions · 20 stateful · 2026-09-20 19:38:21 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,548,649 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w09w010w114w315w416w518w119w220w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd022c24c…ee45
0x34b655…2a6f
14 touches
21 conflicts
0x67a56c8b…f955
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xfe2577ac…677b
0x34b655…2a6f
8 touches
6 conflicts
0x461374ee…f398
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xf9bfdf60…1d24
0x34b655…2a6f
8 touches
6 conflicts
0x5906754f…b584
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xd022c24c1b…0aee45
Audit this contract →
← previous block·next block →recent activity