← previous blocknext block →recent activity
Analyzing
Block #97,501,949
20 transactions · 19 stateful · 2026-08-20 02:04:57 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,501,949 · 20 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
1w02w14w06w27w08w19w110w011w213w115w216w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef08adcc…6fdf
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x76ea4d0a…b4b6
0x34b655…2a6f
6 touches
3 conflicts
0x9287bd11…bb71
0xd32edf…ff58
5 touches
3 conflicts
0x886f7fe6…8b7a
0x34b655…2a6f
4 touches
1 conflict
0x8f63f383…6eda
0x34b655…2a6f
4 touches
1 conflict
0xa21e8abe…a7f1
0x34b655…2a6f
4 touches
1 conflict
0xbc5fc032…8d7e
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 0xef08adccdb…c06fdf
Audit this contract →
← previous block·next block →recent activity