← previous blocknext block →recent activity
Analyzing
Block #97,710,829
18 transactions · 17 stateful · 2026-08-20 19:48:03 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,710,829 · 18 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
1w05w06w17w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x157b6348…8604
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x5120110e…8931
0x34b655…2a6f
4 touches
1 conflict
0x91132a87…2232
0x34b655…2a6f
4 touches
1 conflict
0x9db64d13…fb98
0x34b655…2a6f
4 touches
1 conflict
0x422f657b…279e
0x34b655…2a6f
4 touches
1 conflict
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9284
0x2b46c0…1669
2 touches
0 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
3 conflicts on slot 0x157b634872…098604
Audit this contract →
← previous block·next block →recent activity