← previous blocknext block →recent activity
Analyzing
Block #97,683,506
22 transactions · 20 stateful · 2026-08-20 17:29:13 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,683,506 · 22 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
2w03w14w05w06w17w18w212w213w216w017w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736c5b69…fb3f
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x698bc280…a6d9
0xa6afd3…d132
6 touches
3 conflicts
0x88b255be…0308
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
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 0x736c5b69cc…07fb3f
Audit this contract →
← previous block·next block →recent activity