← previous blocknext block →recent activity
Analyzing
Block #99,615,449
23 transactions · 21 stateful · 2026-08-27 12:36:46 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,615,449 · 23 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
1w02w13w24w29w110w111w213w215w316w417w318w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39ccd26a…4654
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x872e51c8…ae28
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0x39ccd26aaf…a04654
Audit this contract →
← previous block·next block →recent activity