← previous blocknext block →recent activity
Analyzing
Block #106,186,065
23 transactions · 22 stateful · 2026-09-19 13:13:27 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
2.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,186,065 · 23 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
1w02w13w04w19w010w211w212w313w414w515w516w617w721w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x36eb9d19…32f7
0x34b655…2a6f
12 touches
15 conflicts
0x93f90316…2596
0x34b655…2a6f
12 touches
15 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
8 touches
6 conflicts
0x56409df0…27cd
0x34b655…2a6f
6 touches
3 conflicts
0xd41f5136…97c6
0x34b655…2a6f
6 touches
3 conflicts
0x581b829b…9578
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity