← previous blocknext block →recent activity
Analyzing
Block #96,262,609
23 transactions · 21 stateful · 2026-08-15 17:25:38 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,262,609 · 23 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
1w02w14w05w16w27w310w011w112w418w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe8366594…a96e
0x34b655…2a6f
8 touches
6 conflicts
0xd7fccec1…bee0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6b17f7a0…af41
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa9f8096f…f132
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
28 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity