← previous blocknext block →recent activity
Analyzing
Block #97,361,376
16 transactions · 15 stateful · 2026-08-19 13:53:51 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,361,376 · 16 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
1w02w03w04w06w17w28w19w110w211w212w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70a1ac1f…e2d1
0x34b655…2a6f
8 touches
6 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf8982aa7…cbbf
0x34b655…2a6f
6 touches
3 conflicts
0x2ce5d13f…f8a9
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x711ceb8d…5202
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
6 conflicts on slot 0x70a1ac1fbb…a1e2d1
Audit this contract →
← previous block·next block →recent activity