← previous blocknext block →recent activity
Analyzing
Block #97,477,399
22 transactions · 20 stateful · 2026-08-20 00:01:27 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,477,399 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w08w09w010w111w213w214w315w016w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x1dc86774…166a
0x34b655…2a6f
6 touches
3 conflicts
0x1e9dac68…ef8d
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6a13342c…22b6
0x34b655…2a6f
4 touches
1 conflict
0x6f6654bf…2a4d
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 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity