← previous blocknext block →recent activity
Analyzing
Block #99,586,660
22 transactions · 14 stateful · 2026-08-27 10:08:48 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,586,660 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w112w213w315w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe770323…579f
0x34b655…2a6f
6 touches
3 conflicts
0x256341f6…89e9
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf9add8d3…cb7f
0x34b655…2a6f
6 touches
3 conflicts
0x1031484e…d248
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b47a
0x1b6862…e19c
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 0xfe77032353…b7579f
Audit this contract →
← previous block·next block →recent activity