← previous blocknext block →recent activity
Analyzing
Block #98,999,977
14 transactions · 14 stateful · 2026-08-25 08:46:55 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,999,977 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w110w111w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x08399ab6…0057
0x34b655…2a6f
8 touches
6 conflicts
0x5150abbe…43c3
0x34b655…2a6f
6 touches
3 conflicts
0x72411ea8…8b64
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x21e6581c…4357
0x40c49f…2af0
4 touches
1 conflict
0x3258a3d0…e958
0x40c49f…2af0
4 touches
1 conflict
0x94b26b6d…eab2
0x40c49f…2af0
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity