← previous blocknext block →recent activity
Analyzing
Block #97,898,134
22 transactions · 22 stateful · 2026-08-21 11:40:07 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,898,134 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w07w110w011w112w313w414w416w017w118w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x766c38bc…917f
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x2528e717…2a22
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x8aea67a1…8bc9
0x34b655…2a6f
4 touches
1 conflict
0x96b90a93…41d0
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 0x766c38bca6…5a917f
Audit this contract →
← previous block·next block →recent activity