← previous blocknext block →recent activity
Analyzing
Block #97,727,341
21 transactions · 16 stateful · 2026-08-20 21:11:42 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,727,341 · 21 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
2w05w06w18w214w115w317w018w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bc9b1ca…85ef
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xa74e0d23…b452
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x1bc9b1cade…5085ef
Audit this contract →
← previous block·next block →recent activity