← previous blocknext block →recent activity
Analyzing
Block #98,482,231
10 transactions · 9 stateful · 2026-08-23 12:45:31 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,482,231 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x809f2ba8…89d3
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e5afb3a…a338
0x3bd359…433a
2 touches
0 conflicts
0x0fb999ce…da22
0x754704…b603
2 touches
0 conflicts
0x458acedf…f33f
0x754704…b603
2 touches
0 conflicts
0xd15b80ce…8452
0x754704…b603
2 touches
0 conflicts
0xff53b6b2…2f57
0x754704…b603
2 touches
0 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
1 conflict on slot 0x809f2ba80d…9489d3
Audit this contract →
← previous block·next block →recent activity