← previous blocknext block →recent activity
Analyzing
Block #97,741,064
30 transactions · 19 stateful · 2026-08-20 22:20:46 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,741,064 · 30 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
2w04w115w216w317w018w121w023w025w127w228w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0x717205be…1c96
0x065c9d…c394
5 touches
3 conflicts
0x309ef367…e8a1
0x34b655…2a6f
5 touches
3 conflicts
0x15698ac9…2a46
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity