← previous blocknext block →recent activity
Analyzing
Block #97,500,675
19 transactions · 14 stateful · 2026-08-20 01:58:33 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,500,675 · 19 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
2w04w05w08w110w111w213w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd426131…e5d4
0x34b655…2a6f
8 touches
6 conflicts
0x0099420d…37b4
0x34b655…2a6f
8 touches
6 conflicts
0x2264f44c…34f5
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
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
6 conflicts on slot 0xbd426131e8…01e5d4
Audit this contract →
← previous block·next block →recent activity