← previous blocknext block →recent activity
Analyzing
Block #97,551,683
22 transactions · 17 stateful · 2026-08-20 06:15:25 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,551,683 · 22 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
1w04w05w06w07w09w115w116w117w218w119w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6646c80…ea62
0x34b655…2a6f
4 touches
1 conflict
0xf7bfb5fd…cb38
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x38c47502…1005
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xe2263bea…6aa1
0x2b46c0…1669
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
1 conflict on slot 0xe6646c8099…73ea62
Audit this contract →
← previous block·next block →recent activity