← previous blocknext block →recent activity
Analyzing
Block #97,525,661
20 transactions · 18 stateful · 2026-08-20 04:04:15 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,525,661 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w210w312w413w518w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x331a294a…7f59
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x287f71b4…5a6a
0x34b655…2a6f
6 touches
3 conflicts
0x35c37635…11a6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x3a06aac2…c200
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
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
6 conflicts on slot 0x331a294ac1…4d7f59
Audit this contract →
← previous block·next block →recent activity