← previous blocknext block →recent activity
Analyzing
Block #106,235,092
16 transactions · 15 stateful · 2026-09-19 17:20:18 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,235,092 · 16 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
5w08w19w210w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a4230da…3359
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xd4305f3b…7f3e
0x34b655…2a6f
4 touches
1 conflict
0xdec2aeb2…0586
0x34b655…2a6f
2 touches
0 conflicts
0xe8f860c0…35c9
0x34b655…2a6f
2 touches
0 conflicts
0xbfe7fd3a…3168
0x3bd359…433a
2 touches
0 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
3 conflicts on slot 0x6a4230da18…573359
Audit this contract →
← previous block·next block →recent activity