← previous blocknext block →recent activity
Analyzing
Block #106,216,296
15 transactions · 14 stateful · 2026-09-19 15:45:39 UTC
Parallelism
60/100
Blocked
36%
Avg conflicts / tx
1.27
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,216,296 · 15 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
3w07w08w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c4e2024…526c
0x34b655…2a6f
10 touches
10 conflicts
0x94ed2e6a…c6b6
0x34b655…2a6f
10 touches
10 conflicts
0x3287c06e…a95a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
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 0x1c4e2024ad…17526c
Audit this contract →
← previous block·next block →recent activity