← previous blocknext block →recent activity
Analyzing
Block #97,357,967
17 transactions · 13 stateful · 2026-08-19 13:36:13 UTC
Parallelism
65/100
Blocked
54%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,357,967 · 17 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
1w02w04w15w26w38w410w111w012w515w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe2e52e46…0894
0x34b655…2a6f
6 touches
3 conflicts
0xa3f095f5…bd87
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x70a1ac1f…e2d1
0x34b655…2a6f
4 touches
1 conflict
0x8a4ec63f…41c5
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
3 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity