← previous blocknext block →recent activity
Analyzing
Block #97,493,772
26 transactions · 24 stateful · 2026-08-20 01:23:50 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,493,772 · 26 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
1w02w13w25w07w110w011w114w016w217w118w319w320w223w324w425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7bfb5fd…cb38
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xa3b6e4b5…f72c
0x34b655…2a6f
6 touches
3 conflicts
0xdb95e18e…c737
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xf7bfb5fdd1…6acb38
Audit this contract →
← previous block·next block →recent activity