← previous blocknext block →recent activity
Analyzing
Block #97,537,083
17 transactions · 14 stateful · 2026-08-20 05:01:42 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,537,083 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w09w115w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765b5c31…586c
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x06e3a739…7d61
0x34b655…2a6f
2 touches
0 conflicts
0x223dbbdb…4b13
0x34b655…2a6f
2 touches
0 conflicts
0x38c6ff01…689f
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x765b5c3188…52586c
Audit this contract →
← previous block·next block →recent activity