← previous blocknext block →recent activity
Analyzing
Block #97,362,139
20 transactions · 20 stateful · 2026-08-19 13:57:50 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,362,139 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w28w111w213w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22c8341a…7f5f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf020f115…98db
0xd32edf…ff58
5 touches
3 conflicts
0x70f537e8…399b
0x34b655…2a6f
4 touches
1 conflict
0x887bfcdf…13b8
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x12cae920…cbc9
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 0x22c8341a49…b67f5f
Audit this contract →
← previous block·next block →recent activity