← previous blocknext block →recent activity
Analyzing
Block #99,367,023
29 transactions · 19 stateful · 2026-08-26 15:40:09 UTC
Parallelism
86/100
Blocked
53%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,367,023 · 29 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
1w07w18w09w110w011w112w013w114w216w017w121w222w223w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68531239…e9a3
0x34b655…2a6f
8 touches
6 conflicts
0xd3c05624…3417
0x34b655…2a6f
6 touches
3 conflicts
0xe3175d82…2ca0
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x671327de…0812
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xb1b8e78d…34f7
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
6 conflicts on slot 0x68531239f9…5ae9a3
Audit this contract →
← previous block·next block →recent activity