← previous blocknext block →recent activity
Analyzing
Block #97,725,242
22 transactions · 20 stateful · 2026-08-20 21:01:04 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,725,242 · 22 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
1w02w13w04w05w17w08w19w110w211w213w315w417w018w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x247c79f2…e698
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x1cc41f31…cb43
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x422f657b…279e
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0x247c79f2cf…59e698
Audit this contract →
← previous block·next block →recent activity