← previous blocknext block →recent activity
Analyzing
Block #99,249,929
11 transactions · 11 stateful · 2026-08-26 05:50:47 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,249,929 · 11 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
2w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x556beb43…e627
0x34b655…2a6f
4 touches
1 conflict
0x1faeed20…190f
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x98dd86bb…1edb
0x34b655…2a6f
4 touches
1 conflict
0x29cac3f0…d958
0x34b655…2a6f
2 touches
0 conflicts
0x2caeb7f5…b6bb
0x34b655…2a6f
2 touches
0 conflicts
0x2f4f4437…1d3e
0x34b655…2a6f
2 touches
0 conflicts
0x699ee60f…de01
0x34b655…2a6f
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 0x556beb4322…c0e627
Audit this contract →
← previous block·next block →recent activity