← previous blocknext block →recent activity
Analyzing
Block #99,708,621
8 transactions · 7 stateful · 2026-08-27 20:28:29 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,708,621 · 8 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x36836f22…9649
0x34b655…2a6f
3 touches
1 conflict
0xf1611d2d…1605
0x34b655…2a6f
3 touches
1 conflict
0x5da92df7…74b5
0x34b655…2a6f
2 touches
0 conflicts
0x72083f0d…082a
0x34b655…2a6f
2 touches
0 conflicts
0x742436a7…c4d4
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 0x502b3ee1e6…227f7c
Audit this contract →
← previous block·next block →recent activity