← previous blocknext block →recent activity
Analyzing
Block #97,557,770
31 transactions · 27 stateful · 2026-08-20 06:46:37 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,557,770 · 31 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
1w02w06w18w09w010w011w112w115w116w221w222w323w424w225w126w130w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a06d70a…8ba3
0x34b655…2a6f
8 touches
6 conflicts
0xacf0efad…ec2f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x64e1f0ce…7158
0x1b6862…e19c
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 0x8a06d70a65…e68ba3
Audit this contract →
← previous block·next block →recent activity