← previous blocknext block →recent activity
Analyzing
Block #106,199,145
25 transactions · 21 stateful · 2026-09-19 14:19:16 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,199,145 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w212w013w114w215w316w017w119w221w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x029a9f13…cdb2
0x6f6493…b480
7 touches
6 conflicts
0x121ec2bc…8fe5
0x6f6493…b480
7 touches
6 conflicts
0x1768ef05…efa8
0x6f6493…b480
7 touches
6 conflicts
0x27436c91…272a
0x6f6493…b480
7 touches
6 conflicts
0x28d902c5…f079
0x6f6493…b480
7 touches
6 conflicts
0x35069153…9d1a
0x6f6493…b480
7 touches
6 conflicts
0x3a448240…db94
0x6f6493…b480
7 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity