← previous blocknext block →recent activity
Analyzing
Block #97,674,377
36 transactions · 28 stateful · 2026-08-20 16:42:30 UTC
Parallelism
83/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,674,377 · 36 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w011w213w315w416w117w223w224w326w328w429w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736c5b69…fb3f
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xdb519c39…7fd0
0xd32edf…ff58
9 touches
10 conflicts
0x88b255be…0308
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0x736c5b69cc…07fb3f
Audit this contract →
← previous block·next block →recent activity