← previous blocknext block →recent activity
Analyzing
Block #98,385,388
16 transactions · 15 stateful · 2026-08-23 04:37:55 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,385,388 · 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
3w04w18w09w110w111w212w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5934b407…e058
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xfb4fd6ce…262e
0x34b655…2a6f
6 touches
3 conflicts
0xb282d0ed…3561
0x34b655…2a6f
6 touches
3 conflicts
0x82e5ba7e…5254
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xafc3a21b…d25a
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 0x5934b407c2…7fe058
Audit this contract →
← previous block·next block →recent activity