← previous blocknext block →recent activity
Analyzing
Block #99,358,280
37 transactions · 32 stateful · 2026-08-26 14:56:00 UTC
Parallelism
73/100
Blocked
56%
Avg conflicts / tx
1.03
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,358,280 · 37 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
4w06w07w08w19w010w011w112w213w214w315w416w122w423w525w628w129w230w136w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e3e9f18…f684
0x34b655…2a6f
10 touches
10 conflicts
0xd97b0449…00a0
0x34b655…2a6f
8 touches
6 conflicts
0x8947e2e8…cdb3
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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 0x6e3e9f18fd…eff684
Audit this contract →
← previous block·next block →recent activity