← previous blocknext block →recent activity
Analyzing
Block #99,120,395
20 transactions · 14 stateful · 2026-08-25 18:59:06 UTC
Parallelism
85/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,120,395 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w011w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676207a8…5d7e
0x34b655…2a6f
4 touches
1 conflict
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x5f99a57d…4100
0x065c9d…c394
2 touches
0 conflicts
0xdb90b0e4…617f
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x3093e806…bde2
0x34b655…2a6f
2 touches
0 conflicts
0x346e79aa…d01c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x676207a88a…e05d7e
Audit this contract →
← previous block·next block →recent activity