← previous blocknext block →recent activity
Analyzing
Block #97,682,727
26 transactions · 21 stateful · 2026-08-20 17:25:14 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,682,727 · 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
1w02w13w04w15w06w18w09w010w216w317w421w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bc43347…93d4
0x34b655…2a6f
6 touches
3 conflicts
0x605632c2…32e1
0x08cb87…f271
4 touches
1 conflict
0xb318835b…e234
0x08cb87…f271
4 touches
1 conflict
0x00000000…0003
0x103de0…bb55
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
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
3 conflicts on slot 0x0bc433477d…9e93d4
Audit this contract →
← previous block·next block →recent activity