← previous blocknext block →recent activity
Analyzing
Block #98,560,724
20 transactions · 19 stateful · 2026-08-23 19:31:56 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,560,724 · 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
9w010w111w212w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4b350eb…8c96
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0x438f4336…47c9
0x34b655…2a6f
4 touches
1 conflict
0x57676b36…5d4f
0x34b655…2a6f
4 touches
1 conflict
0x5d6e47d8…9ca5
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
3 conflicts on slot 0xb4b350ebf7…dc8c96
Audit this contract →
← previous block·next block →recent activity