← previous blocknext block →recent activity
Analyzing
Block #106,191,200
23 transactions · 20 stateful · 2026-09-19 13:39:17 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,191,200 · 23 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
1w02w13w06w07w18w212w213w314w415w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef4a1ae8…12c9
0x34b655…2a6f
12 touches
15 conflicts
0x6771eae2…7014
0x34b655…2a6f
10 touches
10 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0xd62f3741…b903
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xa9a9d0e0…4087
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 0xef4a1ae8da…e212c9
Audit this contract →
← previous block·next block →recent activity