← previous blocknext block →recent activity
Analyzing
Block #99,790,695
16 transactions · 15 stateful · 2026-08-28 03:24:21 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,790,695 · 16 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
1w04w16w111w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x230d0904…a656
0x34b655…2a6f
8 touches
6 conflicts
0xaa980406…4ae7
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x46611d8f…8963
0x34b655…2a6f
4 touches
1 conflict
0x69234d6d…646d
0x34b655…2a6f
4 touches
1 conflict
0xae6497da…9962
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 0x230d09044b…3aa656
Audit this contract →
← previous block·next block →recent activity