← previous blocknext block →recent activity
Analyzing
Block #97,612,547
17 transactions · 17 stateful · 2026-08-20 11:24:22 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,612,547 · 17 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
2w03w04w05w16w07w18w29w114w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xcb46fee6…837b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3c7d7d48…a7ed
0x34b655…2a6f
4 touches
1 conflict
0x3d8bb490…d81e
0x34b655…2a6f
4 touches
1 conflict
0x6a2ca7be…18a8
0x34b655…2a6f
4 touches
1 conflict
0x721e47d3…d530
0x34b655…2a6f
4 touches
1 conflict
0x7cc587ce…0ae2
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
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity