← previous blocknext block →recent activity
Analyzing
Block #99,089,428
18 transactions · 18 stateful · 2026-08-25 16:23:08 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,089,428 · 18 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
1w02w04w16w07w110w211w312w414w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2d8af24…4750
0x34b655…2a6f
6 touches
3 conflicts
0x1c507f1b…3bf5
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x7e5af856…3a4e
0x34b655…2a6f
4 touches
1 conflict
0x805d08cf…3cfc
0x34b655…2a6f
4 touches
1 conflict
0x8e5003a2…6362
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
3 conflicts on slot 0xb2d8af2470…774750
Audit this contract →
← previous block·next block →recent activity