← previous blocknext block →recent activity
Analyzing
Block #97,613,684
32 transactions · 29 stateful · 2026-08-20 11:30:05 UTC
Parallelism
66/100
Blocked
55%
Avg conflicts / tx
1.66
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #97,613,684 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w08w19w210w311w412w513w419w520w621w722w130w931w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
8 touches
6 conflicts
0xcc9d4fca…ecbf
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2d206566…6aca
0x34b655…2a6f
6 touches
3 conflicts
0x88724b87…5e65
0x34b655…2a6f
4 touches
1 conflict
0x9930adf7…7ea8
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity