← previous blocknext block →recent activity
Analyzing
Block #97,494,241
21 transactions · 21 stateful · 2026-08-20 01:26:11 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,494,241 · 21 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
1w02w03w15w07w08w19w210w311w415w116w217w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x2dcc0868…26bf
0x34b655…2a6f
6 touches
3 conflicts
0x25d909da…1722
0x34b655…2a6f
4 touches
1 conflict
0x2f7060de…7781
0x34b655…2a6f
4 touches
1 conflict
0x35c37635…11a6
0x34b655…2a6f
4 touches
1 conflict
0x41e259ef…b5ac
0x34b655…2a6f
4 touches
1 conflict
0x438f4336…47c9
0x34b655…2a6f
4 touches
1 conflict
0x7ec9cda3…6ddb
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity