← previous blocknext block →recent activity
Analyzing
Block #99,282,811
20 transactions · 17 stateful · 2026-08-26 08:36:17 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,282,811 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w26w07w110w111w112w013w314w415w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x20fcfd39…f28e
0x065c9d…c394
4 touches
3 conflicts
0x45f562b2…9294
0x2b46c0…1669
4 touches
1 conflict
0x48ed1159…abe9
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9354
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9356
0x2b46c0…1669
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
3 conflicts on slot 0x6f132c01d5…7dcdcc
Audit this contract →
← previous block·next block →recent activity