← previous blocknext block →recent activity
Analyzing
Block #98,740,671
26 transactions · 19 stateful · 2026-08-24 11:01:36 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,740,671 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w08w110w011w113w014w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ddfee01…44bb
0x34b655…2a6f
6 touches
3 conflicts
0x00f19757…9252
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0xc7014be1…5d53
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x5ddfee0197…d044bb
Audit this contract →
← previous block·next block →recent activity