← previous blocknext block →recent activity
Analyzing
Block #99,481,033
22 transactions · 22 stateful · 2026-08-27 01:14:15 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,481,033 · 22 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
1w02w13w24w05w16w07w18w29w311w412w514w115w516w617w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48cb599a…c21c
0x34b655…2a6f
10 touches
10 conflicts
0xd9722304…6ed0
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x4e7eb462…b2aa
0x1b6862…e19c
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
10 conflicts on slot 0x48cb599a7b…38c21c
Audit this contract →
← previous block·next block →recent activity