← previous blocknext block →recent activity
Analyzing
Block #97,500,869
33 transactions · 26 stateful · 2026-08-20 01:59:31 UTC
Parallelism
91/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,500,869 · 33 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
2w04w05w16w28w09w110w014w115w116w217w218w023w224w232w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3c91855…d0df
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa0647087…5dd1
0x065c9d…c394
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x6530403a…3ac7
0x065c9d…c394
4 touches
1 conflict
0xbd9491f7…dd92
0x34b655…2a6f
4 touches
1 conflict
0xe9873f38…3274
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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
3 conflicts on slot 0xa3c9185504…b5d0df
Audit this contract →
← previous block·next block →recent activity