← previous blocknext block →recent activity
Analyzing
Block #106,550,921
17 transactions · 17 stateful · 2026-09-20 19:49:47 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,550,921 · 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
4w05w16w27w38w49w510w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
14 touches
21 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x97394169…cfc0
0x34b655…2a6f
14 touches
21 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
12 touches
15 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
12 touches
15 conflicts
0x2f50c84a…3640
0x34b655…2a6f
12 touches
15 conflicts
0x48828733…fd48
0x34b655…2a6f
12 touches
15 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
21 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity