← previous blocknext block →recent activity
Analyzing
Block #99,080,938
27 transactions · 25 stateful · 2026-08-25 15:40:19 UTC
Parallelism
89/100
Blocked
16%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,080,938 · 27 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w113w114w016w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40d6d1e9…131e
0x34b655…2a6f
4 touches
1 conflict
0x1fb8364c…c10d
0x34b655…2a6f
4 touches
1 conflict
0xb55f6c75…c2d2
0xa6afd3…d132
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x648719b8…e97e
0x34b655…2a6f
2 touches
0 conflicts
0x727fbce7…0c80
0x34b655…2a6f
2 touches
0 conflicts
0x7506443a…4820
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 0x40d6d1e99d…4f131e
Audit this contract →
← previous block·next block →recent activity