← previous blocknext block →recent activity
Analyzing
Block #100,978,067
28 transactions · 22 stateful · 2026-09-01 07:05:52 UTC
Parallelism
82/100
Blocked
59%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,978,067 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w07w18w29w210w115w116w219w220w321w324w426w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b3eb43a…ca08
0x34b655…2a6f
10 touches
10 conflicts
0x9d1f0c80…b5b4
0x34b655…2a6f
8 touches
6 conflicts
0x9c6a9da2…c628
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
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
10 conflicts on slot 0x0b3eb43a8c…52ca08
Audit this contract →
← previous block·next block →recent activity