← previous blocknext block →recent activity
Analyzing
Block #97,556,936
31 transactions · 26 stateful · 2026-08-20 06:42:23 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,556,936 · 31 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
1w03w14w25w07w08w19w210w311w215w316w324w027w128w230w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75fe24d2…46f9
0x34b655…2a6f
8 touches
6 conflicts
0xacbf7e91…be17
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xc2aacf41…54ff
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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 0x75fe24d2da…6846f9
Audit this contract →
← previous block·next block →recent activity