← previous blocknext block →recent activity
Analyzing
Block #99,284,573
18 transactions · 16 stateful · 2026-08-26 08:45:09 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,284,573 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w310w112w013w214w316w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26a96f1d…523f
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x6aa624fd…a84f
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
3 conflicts on slot 0x26a96f1d8c…6e523f
Audit this contract →
← previous block·next block →recent activity