← previous blocknext block →recent activity
Analyzing
Block #97,683,576
20 transactions · 19 stateful · 2026-08-20 17:29:34 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,683,576 · 20 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
1w02w03w14w15w06w27w111w115w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736c5b69…fb3f
0x34b655…2a6f
8 touches
6 conflicts
0x41be9e75…9773
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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 0x736c5b69cc…07fb3f
Audit this contract →
← previous block·next block →recent activity