← previous blocknext block →recent activity
Analyzing
Block #99,780,811
16 transactions · 14 stateful · 2026-08-28 02:34:08 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,780,811 · 16 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
1w03w14w29w310w414w015w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08399ab6…0057
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x145a7027…e71a
0x34b655…2a6f
4 touches
1 conflict
0x31d895c6…dc5c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x554873fd…2ff4
0x34b655…2a6f
4 touches
1 conflict
0x5c1b956d…14d3
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 0x08399ab6e2…e00057
Audit this contract →
← previous block·next block →recent activity