← previous blocknext block →recent activity
Analyzing
Block #97,479,704
17 transactions · 16 stateful · 2026-08-20 00:13:03 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,479,704 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w212w313w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe068974d…2117
0x34b655…2a6f
8 touches
6 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbadbadbf…fe21
0x34b655…2a6f
6 touches
3 conflicts
0xcfdbaf59…489a
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
0x34b655…2a6f
6 touches
3 conflicts
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 0xe068974d9a…222117
Audit this contract →
← previous block·next block →recent activity