← previous blocknext block →recent activity
Analyzing
Block #99,477,306
22 transactions · 20 stateful · 2026-08-27 00:55:26 UTC
Parallelism
77/100
Blocked
60%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,477,306 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w09w110w113w114w115w216w317w318w221w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4387ba94…e195
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x593cce97…57ff
0x34b655…2a6f
4 touches
1 conflict
0x5c4b49c3…cc29
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
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
3 conflicts on slot 0x4387ba941b…8be195
Audit this contract →
← previous block·next block →recent activity