← previous blocknext block →recent activity
Analyzing
Block #102,189,279
21 transactions · 21 stateful · 2026-09-05 12:51:23 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,189,279 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w08w19w010w011w112w213w015w316w417w519w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9210e826…1414
0x34b655…2a6f
8 touches
6 conflicts
0x9b153079…4318
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x810bee1d…0817
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
0x34b655…2a6f
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
6 conflicts on slot 0x9210e826c8…c41414
Audit this contract →
← previous block·next block →recent activity