← previous blocknext block →recent activity
Analyzing
Block #97,528,516
22 transactions · 20 stateful · 2026-08-20 04:18:37 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,528,516 · 22 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
1w04w08w09w110w111w212w213w014w116w317w420w521w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7bfb5fd…cb38
0x34b655…2a6f
6 touches
3 conflicts
0x609a25a3…8785
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe6646c80…ea62
0x34b655…2a6f
6 touches
3 conflicts
0x7314325d…2ce2
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x2dcc0868…26bf
0x34b655…2a6f
4 touches
1 conflict
0x35c37635…11a6
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 0xf7bfb5fdd1…6acb38
Audit this contract →
← previous block·next block →recent activity