← previous blocknext block →recent activity
Analyzing
Block #99,358,013
32 transactions · 25 stateful · 2026-08-26 14:54:39 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,358,013 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w013w114w215w216w317w418w019w220w525w026w127w228w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce6b61c0…6e0d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x6e3e9f18…f684
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x84611dd3…b347
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0xce6b61c090…fa6e0d
Audit this contract →
← previous block·next block →recent activity