← previous blocknext block →recent activity
Analyzing
Block #99,270,444
23 transactions · 21 stateful · 2026-08-26 07:34:05 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,270,444 · 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
1w02w04w15w06w18w111w112w213w314w315w116w017w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0xbcd71fd0…3948
0x34b655…2a6f
6 touches
3 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
6 touches
3 conflicts
0x8f2a8b46…fc85
0x34b655…2a6f
6 touches
3 conflicts
0x46abeefb…fc9c
0x34b655…2a6f
4 touches
1 conflict
0x523de645…4f58
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity