← previous blocknext block →recent activity
Analyzing
Block #106,216,588
22 transactions · 21 stateful · 2026-09-19 15:47:07 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,216,588 · 22 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
1w02w13w24w15w26w37w410w515w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f5d6958…8ad9
0x34b655…2a6f
10 touches
10 conflicts
0xe6040987…df02
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xac457663…2f84
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x163c8eca…7b49
0x34b655…2a6f
6 touches
3 conflicts
0xad5de031…c173
0xd32edf…ff58
5 touches
3 conflicts
0xc3e2eeec…e4e0
0x34b655…2a6f
5 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
10 conflicts on slot 0x0f5d695892…188ad9
Audit this contract →
← previous block·next block →recent activity