← previous blocknext block →recent activity
Analyzing
Block #106,397,680
23 transactions · 17 stateful · 2026-09-20 06:58:30 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,397,680 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x65b12d95…0991
0x34b655…2a6f
4 touches
1 conflict
0xa386bf35…7e9f
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x1b4318f0…78fb
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x690117b9…2820
0x3bd359…433a
2 touches
0 conflicts
0x643fa4aa…a822
0x754704…b603
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
1 conflict on slot 0x4984f7bedd…bfd515
Audit this contract →
← previous block·next block →recent activity