← previous blocknext block →recent activity
Analyzing
Block #99,482,234
22 transactions · 21 stateful · 2026-08-27 01:20:18 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,482,234 · 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
1w02w13w04w16w07w18w09w010w111w212w214w115w316w417w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0xae62d2a9…84dd
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdcebb2b8…5f18
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xb1526c23…f2b4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x6427594999…6ed698
Audit this contract →
← previous block·next block →recent activity