← previous blocknext block →recent activity
Analyzing
Block #99,449,767
14 transactions · 13 stateful · 2026-08-26 22:36:48 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,449,767 · 14 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
1w02w13w04w05w16w09w010w211w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf11cf1a…ec04
0x34b655…2a6f
6 touches
3 conflicts
0x1e698c15…d3c5
0x34b655…2a6f
6 touches
3 conflicts
0xa632d1b5…6b9d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xac2a0273…721b
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 0xcf11cf1a8c…15ec04
Audit this contract →
← previous block·next block →recent activity