← previous blocknext block →recent activity
Analyzing
Block #99,879,591
22 transactions · 19 stateful · 2026-08-28 10:53:40 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,879,591 · 22 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
1w04w06w07w110w111w114w015w116w017w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08db2444…22b2
0x34b655…2a6f
6 touches
3 conflicts
0xfaf5fe80…1ffc
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2da9bd33…9117
0x34b655…2a6f
4 touches
1 conflict
0x51af0e92…4020
0x34b655…2a6f
4 touches
1 conflict
0x5c80ed38…84f9
0x34b655…2a6f
4 touches
1 conflict
0x69e7ef29…9a4c
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 0x08db24449d…5f22b2
Audit this contract →
← previous block·next block →recent activity