← previous blocknext block →recent activity
Analyzing
Block #98,414,615
14 transactions · 14 stateful · 2026-08-23 07:04:58 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,414,615 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w37w08w19w410w511w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdd556aa…31d0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xda5c80a5…4a0d
0x34b655…2a6f
6 touches
3 conflicts
0xbc3b2976…3e11
0x34b655…2a6f
6 touches
3 conflicts
0x4d2e63d6…ba5e
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
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 0xcdd556aab1…2c31d0
Audit this contract →
← previous block·next block →recent activity