← previous blocknext block →recent activity
Analyzing
Block #106,216,163
28 transactions · 27 stateful · 2026-09-19 15:44:59 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,216,163 · 28 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
2w03w14w25w07w08w112w113w216w217w318w319w420w523w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4118bd12…924a
0x34b655…2a6f
8 touches
6 conflicts
0x94ed2e6a…c6b6
0x34b655…2a6f
8 touches
6 conflicts
0x86ea987c…5a81
0x34b655…2a6f
8 touches
6 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0x039c2af0…720b
0x34b655…2a6f
8 touches
6 conflicts
0xe3323113…90fd
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
8 touches
6 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 0x4118bd1265…fa924a
Audit this contract →
← previous block·next block →recent activity