← previous blocknext block →recent activity
Analyzing
Block #97,726,679
19 transactions · 17 stateful · 2026-08-20 21:08:22 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,726,679 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w27w311w412w513w114w217w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91132a87…2232
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x78fb904c…7643
0x34b655…2a6f
8 touches
6 conflicts
0x63926e81…db28
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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
10 conflicts on slot 0x91132a87ef…ed2232
Audit this contract →
← previous block·next block →recent activity