← previous blocknext block →recent activity
Analyzing
Block #97,497,302
30 transactions · 27 stateful · 2026-08-20 01:41:35 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,497,302 · 30 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
1w04w05w16w17w28w29w316w118w320w428w029w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x886f7fe6…8b7a
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xfccb8789…b30b
0x34b655…2a6f
4 touches
1 conflict
0x06c59b8c…89c0
0x34b655…2a6f
4 touches
1 conflict
0x3def3fad…b5ee
0x34b655…2a6f
4 touches
1 conflict
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0x728f999a…832f
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 0x886f7fe654…c88b7a
Audit this contract →
← previous block·next block →recent activity