← previous blocknext block →recent activity
Analyzing
Block #97,844,209
20 transactions · 19 stateful · 2026-08-21 07:01:59 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,844,209 · 20 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
1w02w14w05w16w27w08w19w210w311w112w214w015w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05b82e92…351d
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x641245e3…6323
0xc8689a…ee79
4 touches
1 conflict
0x14f3db86…c03e
0x34b655…2a6f
4 touches
1 conflict
0x1a979328…3f6a
0x34b655…2a6f
4 touches
1 conflict
0xcd041b2c…d016
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
3 conflicts on slot 0x05b82e92aa…da351d
Audit this contract →
← previous block·next block →recent activity