← previous blocknext block →recent activity
Analyzing
Block #98,581,678
15 transactions · 14 stateful · 2026-08-23 21:21:12 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,581,678 · 15 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
2w03w14w212w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b10f1de…fc43
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x456ccc15…e999
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
2 touches
0 conflicts
0x7a9fa7e8…3bd9
0x34b655…2a6f
2 touches
0 conflicts
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 0x0b10f1de2a…acfc43
Audit this contract →
← previous block·next block →recent activity