← previous blocknext block →recent activity
Analyzing
Block #97,502,669
18 transactions · 17 stateful · 2026-08-20 02:08:35 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,502,669 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w18w29w310w411w213w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0012270b…67b2
0x34b655…2a6f
6 touches
3 conflicts
0xb975c6fd…bb64
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6b454214…4dd4
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0xa7481e1f…531f
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 0x0012270b7d…5d67b2
Audit this contract →
← previous block·next block →recent activity