← previous blocknext block →recent activity
Analyzing
Block #98,380,281
20 transactions · 19 stateful · 2026-08-23 04:12:14 UTC
Parallelism
85/100
Blocked
26%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,380,281 · 20 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
1w03w04w110w111w212w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ecbbe7…f713
0x34b655…2a6f
6 touches
3 conflicts
0xf6884b1c…8b7f
0x34b655…2a6f
4 touches
1 conflict
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xeca74ff3…a361
0x34b655…2a6f
4 touches
1 conflict
0x12e7c471…901c
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 0xa7ecbbe767…04f713
Audit this contract →
← previous block·next block →recent activity