← previous blocknext block →recent activity
Analyzing
Block #99,977,332
17 transactions · 16 stateful · 2026-08-28 19:06:12 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,977,332 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w19w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2de1aea…8024
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x627738d1…db02
0x34b655…2a6f
4 touches
1 conflict
0x05d5f037…360f
0x34b655…2a6f
2 touches
0 conflicts
0x1f024fc1…fffc
0x34b655…2a6f
2 touches
0 conflicts
0x1f92241e…8f8b
0x34b655…2a6f
2 touches
0 conflicts
0x2f4f4437…1d3e
0x34b655…2a6f
2 touches
0 conflicts
0x5e917f4c…9730
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 0xe2de1aeae5…be8024
Audit this contract →
← previous block·next block →recent activity