← previous blocknext block →recent activity
Analyzing
Block #97,727,093
18 transactions · 17 stateful · 2026-08-20 21:10:27 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,727,093 · 18 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
1w04w05w16w09w110w211w213w317w1
- 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
0xa554d0c5…22dd
0x34b655…2a6f
6 touches
3 conflicts
0x11b3bcf6…fe81
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x89dd72df…8c3a
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0xc2019d5b…0332
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