← previous blocknext block →recent activity
Analyzing
Block #99,588,912
24 transactions · 20 stateful · 2026-08-27 10:20:17 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,588,912 · 24 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
4w07w18w09w010w111w212w317w419w521w022w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53c41998…7d52
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x021cd478…a6d4
0x34b655…2a6f
6 touches
3 conflicts
0xcbbd3473…0bff
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
5 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
15 conflicts on slot 0x53c41998b8…357d52
Audit this contract →
← previous block·next block →recent activity