← previous blocknext block →recent activity
Analyzing
Block #97,665,832
17 transactions · 17 stateful · 2026-08-20 15:58:20 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,665,832 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w27w38w411w012w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xc0988d33…e5c6
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x9db64d13…fb98
0x34b655…2a6f
6 touches
3 conflicts
0x4a0337ba…97cc
0x34b655…2a6f
4 touches
1 conflict
0x77320d72…3cd9
0x34b655…2a6f
4 touches
1 conflict
0x7d27dcec…508c
0x34b655…2a6f
4 touches
1 conflict
0x0398c745…05d0
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
6 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity