← previous blocknext block →recent activity
Analyzing
Block #97,516,958
28 transactions · 25 stateful · 2026-08-20 03:20:29 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,516,958 · 28 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
2w06w07w08w19w110w212w013w016w117w120w221w323w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d354ff0…b7c5
0x34b655…2a6f
6 touches
3 conflicts
0xb5924647…4cf1
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x21d6593f…26e1
0x34b655…2a6f
4 touches
1 conflict
0x38c47502…1005
0x34b655…2a6f
4 touches
1 conflict
0x4189ab43…4da7
0x34b655…2a6f
4 touches
1 conflict
0x61f7bce8…3e84
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 0x3d354ff0ba…48b7c5
Audit this contract →
← previous block·next block →recent activity