← previous blocknext block →recent activity
Analyzing
Block #97,478,593
13 transactions · 11 stateful · 2026-08-20 00:07:28 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,478,593 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x015a51cb…b7b7
0x34b655…2a6f
4 touches
1 conflict
0xcb46fee6…837b
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0176b0fe…e12c
0x34b655…2a6f
4 touches
1 conflict
0x0179e71d…e168
0x34b655…2a6f
2 touches
0 conflicts
0x05864369…6d7d
0x34b655…2a6f
2 touches
0 conflicts
0x3c7d7d48…a7ed
0x34b655…2a6f
2 touches
0 conflicts
0x747f609d…1555
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
1 conflict on slot 0x015a51cb01…f4b7b7
Audit this contract →
← previous block·next block →recent activity