← previous blocknext block →recent activity
Analyzing
Block #97,740,782
35 transactions · 24 stateful · 2026-08-20 22:19:21 UTC
Parallelism
89/100
Blocked
42%
Avg conflicts / tx
0.49
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,740,782 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w011w112w213w314w115w217w020w021w122w223w332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
8 touches
6 conflicts
0x41d8db70…8c2f
0xd32edf…ff58
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x51ca3051…0972
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x614b85…a284
4 touches
1 conflict
0x00000000…0003
0x614b85…a284
4 touches
1 conflict
0x00000000…0004
0x614b85…a284
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: 0x103de0b5…25bb55
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity