← previous blocknext block →recent activity
Analyzing
Block #97,710,931
12 transactions · 11 stateful · 2026-08-20 19:48:34 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,710,931 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9db64d13…fb98
0x34b655…2a6f
6 touches
3 conflicts
0x668b7b95…7982
0x34b655…2a6f
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x864746b7…9b26
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x7bdccbcd…6bed
0x40c49f…2af0
2 touches
0 conflicts
0x7f4d83f9…b738
0x40c49f…2af0
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
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 0x9db64d13f5…6efb98
Audit this contract →
← previous block·next block →recent activity