← previous blocknext block →recent activity
Analyzing
Block #99,086,245
30 transactions · 28 stateful · 2026-08-25 16:07:05 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,086,245 · 30 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
1w03w04w18w19w210w311w213w014w115w016w118w320w221w423w428w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x820d7282…6c34
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xa02838a3…bc54
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x9e1c65d0…77a3
0x34b655…2a6f
4 touches
1 conflict
0xcc6e2e88…6569
0x34b655…2a6f
4 touches
1 conflict
0xe2d2fc6c…a41a
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
6 conflicts on slot 0x820d72829e…536c34
Audit this contract →
← previous block·next block →recent activity