← previous blocknext block →recent activity
Analyzing
Block #106,388,921
17 transactions · 17 stateful · 2026-09-20 06:14:25 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,388,921 · 17 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
5w09w110w212w213w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40c584a0…3f07
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0x65289e13…8416
0x34b655…2a6f
4 touches
1 conflict
0x7aa5d2c4…d6ef
0x34b655…2a6f
4 touches
1 conflict
0x7fd55c5f…1f35
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
10 conflicts on slot 0x40c584a0fc…ad3f07
Audit this contract →
← previous block·next block →recent activity