← previous blocknext block →recent activity
Analyzing
Block #97,916,642
25 transactions · 20 stateful · 2026-08-21 13:14:25 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,916,642 · 25 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
5w07w18w29w010w111w212w014w321w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
6 touches
3 conflicts
0x10d80fee…dbda
0x2b46c0…1669
6 touches
3 conflicts
0x2f4b2cf9…4e1e
0x2b46c0…1669
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
6 touches
3 conflicts
0x7aa91b8f…d070
0x2b46c0…1669
6 touches
3 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity