← previous blocknext block →recent activity
Analyzing
Block #97,370,241
25 transactions · 21 stateful · 2026-08-19 14:39:14 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,370,241 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w28w39w416w517w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x392f42be…733c
0x34b655…2a6f
12 touches
15 conflicts
0x4e37574f…4145
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
5 conflicts
0x289ce6b2…d0ae
0x34b655…2a6f
6 touches
5 conflicts
0x00000000…004c
0x80c745…7210
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity