← previous blocknext block →recent activity
Analyzing
Block #99,495,238
26 transactions · 26 stateful · 2026-08-27 02:25:46 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,495,238 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w07w19w110w011w213w114w215w018w120w221w124w125w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc95f91db…a901
0x34b655…2a6f
6 touches
3 conflicts
0xdd6538fb…2b3f
0x34b655…2a6f
6 touches
3 conflicts
0xe681e747…b48c
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xc95f91db39…24a901
Audit this contract →
← previous block·next block →recent activity