← previous blocknext block →recent activity
Analyzing
Block #97,605,301
26 transactions · 20 stateful · 2026-08-20 10:47:25 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,605,301 · 26 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
2w04w05w16w18w216w317w425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e5cdd04…22ab
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x8f571b61…16d8
0x34b655…2a6f
4 touches
1 conflict
0xa9bfe74b…fd26
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc9d4fca…ecbf
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 0x2e5cdd041a…6e22ab
Audit this contract →
← previous block·next block →recent activity