← previous blocknext block →recent activity
Analyzing
Block #97,496,422
21 transactions · 18 stateful · 2026-08-20 01:37:09 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,496,422 · 21 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
1w02w05w16w27w38w49w510w413w214w315w016w117w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x015a51cb…b7b7
0x34b655…2a6f
8 touches
6 conflicts
0xc4126b38…e604
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x59a84baf…4dfa
0x34b655…2a6f
4 touches
1 conflict
0x6737ee07…9978
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x809f2ba8…89d3
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 0x015a51cb01…f4b7b7
Audit this contract →
← previous block·next block →recent activity