← previous blocknext block →recent activity
Analyzing
Block #97,521,262
15 transactions · 13 stateful · 2026-08-20 03:42:08 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,521,262 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w08w113w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f7ff624…a642
0x34b655…2a6f
4 touches
1 conflict
0xe5a17dc1…4b7f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7061d006…074d
0x34b655…2a6f
2 touches
0 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x2f7ff6242e…fda642
Audit this contract →
← previous block·next block →recent activity