← previous blocknext block →recent activity
Analyzing
Block #97,368,458
32 transactions · 23 stateful · 2026-08-19 14:30:09 UTC
Parallelism
84/100
Blocked
57%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,368,458 · 32 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
1w02w13w04w05w110w211w112w215w216w317w218w119w220w021w129w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
6 touches
3 conflicts
0xfe20f99f…a42a
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x5d863b2f…bd28
0x34b655…2a6f
6 touches
3 conflicts
0x5117b618…5f5f
0x34b655…2a6f
6 touches
3 conflicts
0x1caa8c00…cb39
0xd32edf…ff58
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity