← previous blocknext block →recent activity
Analyzing
Block #99,980,168
16 transactions · 16 stateful · 2026-08-28 19:20:28 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,980,168 · 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
5w06w18w29w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x664fee5f…554b
0x34b655…2a6f
8 touches
6 conflicts
0x08f39e39…ed46
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d7edd…8a03
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x1e737223…2278
0x34b655…2a6f
6 touches
3 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0x25be7ab9…0e12
0x34b655…2a6f
4 touches
1 conflict
0x2d82b7d5…cc2f
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 0x664fee5fc9…c0554b
Audit this contract →
← previous block·next block →recent activity