← previous blocknext block →recent activity
Analyzing
Block #99,457,332
11 transactions · 11 stateful · 2026-08-26 23:14:53 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,457,332 · 11 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
1w03w05w16w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a39a2a4…857b
0x34b655…2a6f
6 touches
3 conflicts
0x4d1c169c…e130
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x2ac30c66…8a23
0x34b655…2a6f
6 touches
3 conflicts
0x998a1167…81f9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x4a39a2a411…a6857b
Audit this contract →
← previous block·next block →recent activity