← previous blocknext block →recent activity
Analyzing
Block #99,849,271
22 transactions · 21 stateful · 2026-08-28 08:20:47 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,849,271 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w19w110w213w114w218w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5893393…464c
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9294
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0a8f8b9c…3046
0x34b655…2a6f
4 touches
1 conflict
0x0d2d23d3…8a3a
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
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
1 conflict on slot 0xf5893393e9…d8464c
Audit this contract →
← previous block·next block →recent activity