← previous blocknext block →recent activity
Analyzing
Block #99,587,113
37 transactions · 35 stateful · 2026-08-27 10:11:07 UTC
Parallelism
78/100
Blocked
60%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,587,113 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w18w09w111w112w013w114w215w319w420w521w123w624w725w126w227w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x888660ec…c3eb
0x34b655…2a6f
10 touches
10 conflicts
0xb7d7224e…1b41
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0x75dd818d…df4c
0x34b655…2a6f
7 touches
6 conflicts
0xfd401f8a…aae5
0xa6afd3…d132
6 touches
3 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity