← previous blocknext block →recent activity
Analyzing
Block #106,198,414
17 transactions · 17 stateful · 2026-09-19 14:15:36 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,198,414 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w412w514w015w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
8 touches
6 conflicts
0x634015e1…0b09
0x34b655…2a6f
8 touches
6 conflicts
0x7eb3ae1e…a1a3
0x34b655…2a6f
6 touches
3 conflicts
0x88fc2a68…3918
0x34b655…2a6f
6 touches
3 conflicts
0x98dd86bb…1edb
0x34b655…2a6f
6 touches
3 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity