← previous blocknext block →recent activity
Analyzing
Block #99,211,536
17 transactions · 16 stateful · 2026-08-26 02:37:36 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
1.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,211,536 · 17 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
1w02w14w25w06w27w38w29w010w113w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xaf68eea4…f271
0xd32edf…ff58
5 touches
3 conflicts
0x5c1b956d…14d3
0x34b655…2a6f
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity