← previous blocknext block →recent activity
Analyzing
Block #106,193,435
31 transactions · 26 stateful · 2026-09-19 13:50:32 UTC
Parallelism
65/100
Blocked
62%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,193,435 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w213w314w418w220w721w322w823w424w925w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x8d175439…fb79
0x34b655…2a6f
10 touches
10 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0x3b294b21…8cf8
0x34b655…2a6f
10 touches
10 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
10 touches
10 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity