← previous blocknext block →recent activity
Analyzing
Block #106,576,208
17 transactions · 16 stateful · 2026-09-20 21:57:03 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,576,208 · 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
3w05w06w17w28w312w113w415w016w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x2f50c84a…3640
0x34b655…2a6f
6 touches
3 conflicts
0x48828733…fd48
0x34b655…2a6f
6 touches
3 conflicts
0x4a45b318…9716
0x34b655…2a6f
6 touches
3 conflicts
0x556beb43…e627
0x34b655…2a6f
6 touches
3 conflicts
0x69d2053b…935a
0x34b655…2a6f
6 touches
3 conflicts
0x7aa463de…e7b8
0x34b655…2a6f
6 touches
3 conflicts
0xa57a72ed…64c2
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity