← previous blocknext block →recent activity
Analyzing
Block #97,364,042
25 transactions · 17 stateful · 2026-08-19 14:07:39 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,364,042 · 25 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
2w04w05w06w19w010w211w112w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbe54b7d5…1bda
0x34b655…2a6f
6 touches
3 conflicts
0xfc3d5171…8357
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x45ef9175…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x46242ecc…d0f7
0x34b655…2a6f
4 touches
1 conflict
0x8b94b834…8712
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity