← previous blocknext block →recent activity
Analyzing
Block #105,538,894
19 transactions · 18 stateful · 2026-09-17 06:53:45 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,538,894 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w09w110w212w113w215w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd9ee913b…710e
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0x06dc7f4e…0676
0x6f6493…b480
6 touches
3 conflicts
0x08e07a85…be89
0x6f6493…b480
6 touches
3 conflicts
0x208634ff…b8e0
0x6f6493…b480
6 touches
3 conflicts
0x22c68176…35d9
0x6f6493…b480
6 touches
3 conflicts
0x2b80b8ae…90c1
0x6f6493…b480
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity