← previous blocknext block →recent activity
Analyzing
Block #97,671,328
15 transactions · 14 stateful · 2026-08-20 16:26:37 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,671,328 · 15 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
4w05w16w07w18w010w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb37d3e7…d2be
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x85bfd0af…ce96
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xec7d120d…7084
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 0xbb37d3e789…85d2be
Audit this contract →
← previous block·next block →recent activity