← previous blocknext block →recent activity
Analyzing
Block #97,898,224
18 transactions · 17 stateful · 2026-08-21 11:40:34 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,898,224 · 18 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
2w03w14w26w07w18w310w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22455da…1ce1
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3b2dfb32…949b
0x34b655…2a6f
4 touches
1 conflict
0xe2d50773…c39e
0x34b655…2a6f
4 touches
1 conflict
0x00419ad1…8d3c
0x34b655…2a6f
4 touches
1 conflict
0x0d8152a0…f7f4
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 0xe22455dad4…031ce1
Audit this contract →
← previous block·next block →recent activity