← previous blocknext block →recent activity
Analyzing
Block #97,827,312
17 transactions · 16 stateful · 2026-08-21 05:36:12 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,827,312 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w18w09w210w313w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x103e4080…0d3a
0x34b655…2a6f
6 touches
3 conflicts
0xe38f7c29…72fc
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6cd42192…08f3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf6cc0589…5104
0x34b655…2a6f
4 touches
1 conflict
0x44e7b8f0…96e9
0x34b655…2a6f
4 touches
1 conflict
0x46483cb1…e7ca
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 0x103e408028…c20d3a
Audit this contract →
← previous block·next block →recent activity