← previous blocknext block →recent activity
Analyzing
Block #106,235,686
24 transactions · 19 stateful · 2026-09-19 17:23:17 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,235,686 · 24 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
3w010w012w115w217w318w419w020w121w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7e616bb…94ec
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xf9470055…bbf8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x87b91d84…7cd3
0x34b655…2a6f
4 touches
1 conflict
0x8ca2ca3b…d872
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
6 conflicts on slot 0xe7e616bb13…b394ec
Audit this contract →
← previous block·next block →recent activity