← previous blocknext block →recent activity
Analyzing
Block #105,605,418
19 transactions · 19 stateful · 2026-09-17 12:28:36 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,605,418 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w110w212w213w114w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b42f6a7…f49c
0x34b655…2a6f
6 touches
3 conflicts
0x8da27f7c…31da
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0xf984d8ab…6e4f
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x158f53c0…6445
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x7b42f6a7e5…ebf49c
Audit this contract →
← previous block·next block →recent activity