← previous blocknext block →recent activity
Analyzing
Block #99,875,508
17 transactions · 15 stateful · 2026-08-28 10:33:05 UTC
Parallelism
53/100
Blocked
60%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,875,508 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w49w513w615w716w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc16e646d…4fb0
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5d114832…03a4
0x34b655…2a6f
8 touches
6 conflicts
0x5e945b27…5a12
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd5b10148…e631
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0a2131b3…455e
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
10 conflicts on slot 0xc16e646d81…a44fb0
Audit this contract →
← previous block·next block →recent activity