← previous blocknext block →recent activity
Analyzing
Block #95,902,581
7 transactions · 7 stateful · 2026-08-14 11:14:26 UTC
Parallelism
29/100
Blocked
57%
Avg conflicts / tx
1.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,902,581 · 7 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
1w02w13w24w35w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfd33a92…5c35
0x34b655…2a6f
10 touches
10 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
6 touches
3 conflicts
0x3944526b…c457
0x34b655…2a6f
4 touches
1 conflict
0x45911da6…5523
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0xbfd33a920c…0a5c35
Audit this contract →
← previous block·next block →recent activity