← previous blocknext block →recent activity
Analyzing
Block #99,483,030
23 transactions · 23 stateful · 2026-08-27 01:24:18 UTC
Parallelism
57/100
Blocked
61%
Avg conflicts / tx
2.48
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,483,030 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w29w310w412w513w614w716w517w818w919w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002ba345…90c2
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x0a6cb118…4ca3
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0x002ba3455a…3690c2
Audit this contract →
← previous block·next block →recent activity