← previous blocknext block →recent activity
Analyzing
Block #106,921,778
19 transactions · 19 stateful · 2026-09-22 02:57:21 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,921,778 · 19 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
1w04w07w18w29w310w411w512w613w718w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x7ca519d1…4f93
0x34b655…2a6f
14 touches
21 conflicts
0xe5113c90…6d10
0x34b655…2a6f
4 touches
1 conflict
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x34ae4d…3fc5
2 touches
0 conflicts
0x8e2aea13…258c
0x34b655…2a6f
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
28 conflicts on slot 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity