← previous blocknext block →recent activity
Analyzing
Block #99,284,595
19 transactions · 17 stateful · 2026-08-26 08:45:16 UTC
Parallelism
68/100
Blocked
29%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,284,595 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62910921…3016
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
8 touches
6 conflicts
0x57be321f…fecc
0x34b655…2a6f
7 touches
6 conflicts
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0x97785d36…2ac5
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
10 conflicts on slot 0x629109215a…273016
Audit this contract →
← previous block·next block →recent activity