← previous blocknext block →recent activity
Analyzing
Block #99,161,911
27 transactions · 23 stateful · 2026-08-25 22:27:57 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,161,911 · 27 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
3w04w16w07w113w114w115w216w017w219w321w323w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x7c68d10b…8386
0x34b655…2a6f
6 touches
3 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
4 touches
1 conflict
0x920754e8…0ac6
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity