← previous blocknext block →recent activity
Analyzing
Block #99,709,802
14 transactions · 14 stateful · 2026-08-27 20:34:26 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,709,802 · 14 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
4w05w16w07w18w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9d11061…b7e9
0x34b655…2a6f
8 touches
6 conflicts
0x08399ab6…0057
0x34b655…2a6f
6 touches
3 conflicts
0xf756c90b…3e72
0x34b655…2a6f
6 touches
3 conflicts
0xc6df3bf1…6fec
0x34b655…2a6f
6 touches
3 conflicts
0x5b68c568…9210
0x34b655…2a6f
6 touches
3 conflicts
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0xbac338fb…5aec
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0xa9d110613e…d3b7e9
Audit this contract →
← previous block·next block →recent activity