← previous blocknext block →recent activity
Analyzing
Block #97,818,766
13 transactions · 12 stateful · 2026-08-21 04:53:04 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,818,766 · 13 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
1w02w04w15w16w27w210w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4de40a98…ee65
0x34b655…2a6f
6 touches
3 conflicts
0xaaa40a27…27cd
0x34b655…2a6f
6 touches
3 conflicts
0x7316dc00…c16a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ce27151…5a74
0x34b655…2a6f
4 touches
1 conflict
0x75355859…229c
0x34b655…2a6f
4 touches
1 conflict
0x7975e059…379b
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 0x4de40a988e…f8ee65
Audit this contract →
← previous block·next block →recent activity