← previous blocknext block →recent activity
Analyzing
Block #102,444,421
20 transactions · 16 stateful · 2026-09-06 10:23:56 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,444,421 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w08w113w214w315w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d6b9af1…9a38
0x34b655…2a6f
6 touches
3 conflicts
0xab7f4e6b…8093
0x34b655…2a6f
6 touches
3 conflicts
0x6636a104…d595
0x34b655…2a6f
6 touches
3 conflicts
0xc721193a…b225
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
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
3 conflicts on slot 0x7d6b9af162…f89a38
Audit this contract →
← previous block·next block →recent activity