← previous blocknext block →recent activity
Analyzing
Block #99,871,530
30 transactions · 26 stateful · 2026-08-28 10:13:03 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,871,530 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w011w112w213w314w415w516w627w429w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x21a1d259…eda5
0x34b655…2a6f
8 touches
6 conflicts
0x140145b5…0e95
0x34b655…2a6f
6 touches
3 conflicts
0x2e823c65…b938
0x34b655…2a6f
6 touches
3 conflicts
0xcf61f287…3f4e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1f77ce8f…f484
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity