← previous blocknext block →recent activity
Analyzing
Block #97,989,360
21 transactions · 20 stateful · 2026-08-21 19:24:09 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,989,360 · 21 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
1w02w13w04w25w06w19w010w114w315w117w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9c17729…ac91
0x34b655…2a6f
8 touches
6 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
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xea2d3331…6e33
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xc9c17729ae…44ac91
Audit this contract →
← previous block·next block →recent activity