← previous blocknext block →recent activity
Analyzing
Block #97,494,500
23 transactions · 23 stateful · 2026-08-20 01:27:29 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
1.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,494,500 · 23 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
1w02w03w04w15w16w17w28w29w310w111w014w015w216w318w319w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1dc86774…166a
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x28f324ed…9db7
0x34b655…2a6f
6 touches
3 conflicts
0xda1f3e2c…b73d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x6c0e32fc…a6ca
0x34b655…2a6f
4 touches
1 conflict
0x8902ba1f…f4b6
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 0x1dc86774a8…36166a
Audit this contract →
← previous block·next block →recent activity