← previous blocknext block →recent activity
Analyzing
Block #97,565,862
31 transactions · 29 stateful · 2026-08-20 07:27:59 UTC
Parallelism
87/100
Blocked
28%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,565,862 · 31 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
1w02w05w07w08w19w110w212w216w122w027w028w129w330w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cfec795…7c0e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xcbe3d993…52dd
0x34b655…2a6f
4 touches
1 conflict
0xcd027f38…15b7
0x34b655…2a6f
4 touches
1 conflict
0xd12de736…3f37
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x5cfec7957f…867c0e
Audit this contract →
← previous block·next block →recent activity