← previous blocknext block →recent activity
Analyzing
Block #95,552,082
14 transactions · 14 stateful · 2026-08-13 05:50:18 UTC
Parallelism
57/100
Blocked
71%
Avg conflicts / tx
2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,552,082 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w17w28w39w410w513w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7608886…4340
0x34b655…2a6f
12 touches
15 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x6254804c…a03b
0x34b655…2a6f
4 touches
1 conflict
0x64c6190b…498c
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0x774814a4…2bd6
0x34b655…2a6f
4 touches
1 conflict
0x803eb45d…00bd
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
15 conflicts on slot 0xd7608886a7…504340
Audit this contract →
← previous block·next block →recent activity