← previous blocknext block →recent activity
Analyzing
Block #97,671,347
27 transactions · 25 stateful · 2026-08-20 16:26:42 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,671,347 · 27 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
2w03w14w05w16w28w09w010w111w114w015w117w218w321w326w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06a27525…f082
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x31c190a0…b484
0x065c9d…c394
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3df3de0d…cd8b
0x34b655…2a6f
4 touches
1 conflict
0x41be9e75…9773
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
3 conflicts on slot 0x06a2752594…3af082
Audit this contract →
← previous block·next block →recent activity