← previous blocknext block →recent activity
Analyzing
Block #98,654,123
20 transactions · 20 stateful · 2026-08-24 03:38:26 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,654,123 · 20 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
1w05w16w28w011w116w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x61ca6437…2142
0x34b655…2a6f
6 touches
3 conflicts
0x81932ded…6946
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
0x34b655…2a6f
4 touches
1 conflict
0x6d352690…6b75
0x3bd359…433a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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