← previous blocknext block →recent activity
Analyzing
Block #106,397,228
22 transactions · 21 stateful · 2026-09-20 06:56:14 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,397,228 · 22 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
1w02w14w06w110w111w213w115w016w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x558eafff…804d
0x34b655…2a6f
8 touches
6 conflicts
0xa6b0d9eb…82ac
0x34b655…2a6f
8 touches
6 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
8 touches
6 conflicts
0x9c2fc330…0091
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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 0x558eafff78…04804d
Audit this contract →
← previous block·next block →recent activity