← previous blocknext block →recent activity
Analyzing
Block #99,625,961
35 transactions · 32 stateful · 2026-08-27 13:30:47 UTC
Parallelism
86/100
Blocked
66%
Avg conflicts / tx
0.97
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,625,961 · 35 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
1w02w13w24w06w37w39w110w111w112w213w314w015w116w220w321w322w423w324w125w227w428w333w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39ccd26a…4654
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x0f43bfc7…1de5
0x34b655…2a6f
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