← previous blocknext block →recent activity
Analyzing
Block #106,413,310
24 transactions · 23 stateful · 2026-09-20 08:17:09 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,413,310 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w011w013w114w315w416w317w518w420w121w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd131fa…dbdb
0x34b655…2a6f
14 touches
21 conflicts
0xf51ddc84…51c6
0x34b655…2a6f
12 touches
15 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
12 touches
15 conflicts
0x74e46435…fdcd
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xe0c1cab7…4e51
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xa1524d24…57bc
0x34b655…2a6f
6 touches
3 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 0xfdd131fae1…f8dbdb
Audit this contract →
← previous block·next block →recent activity