← previous blocknext block →recent activity
Analyzing
Block #97,361,631
30 transactions · 23 stateful · 2026-08-19 13:55:10 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.97
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,361,631 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w010w111w112w218w219w221w322w423w528w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3f6f7c8…2436
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xe2e52e46…0894
0x34b655…2a6f
6 touches
3 conflicts
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0xd0e7796c…fd59
0xd32edf…ff58
5 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa3f095f5…bd87
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 0xa3f6f7c8bd…f22436
Audit this contract →
← previous block·next block →recent activity