← previous blocknext block →recent activity
Analyzing
Block #97,732,245
17 transactions · 17 stateful · 2026-08-20 21:36:24 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,732,245 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w07w08w19w111w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5896c239…b76c
0x34b655…2a6f
6 touches
3 conflicts
0xa3076829…033c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x68c23664…74c4
0x34b655…2a6f
4 touches
1 conflict
0x91220b8f…7a06
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
3 conflicts on slot 0x5896c2397f…62b76c
Audit this contract →
← previous block·next block →recent activity