← previous blocknext block →recent activity
Analyzing
Block #97,841,250
26 transactions · 23 stateful · 2026-08-21 06:46:45 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,841,250 · 26 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
2w05w06w08w19w210w113w216w319w120w321w222w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6423fcab…a7c1
0x34b655…2a6f
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…7223
0x34b655…2a6f
4 touches
1 conflict
0x4211bf04…1bba
0x065c9d…c394
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
6 conflicts on slot 0x6423fcabc9…18a7c1
Audit this contract →
← previous block·next block →recent activity