← previous blocknext block →recent activity
Analyzing
Block #95,642,656
15 transactions · 13 stateful · 2026-08-13 13:25:52 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,642,656 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w08w110w011w212w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69c491e3…98d9
0x34b655…2a6f
6 touches
3 conflicts
0xad631952…e126
0x34b655…2a6f
6 touches
3 conflicts
0x92132ed7…2722
0x34b655…2a6f
6 touches
3 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0x3f78072a…d0be
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5bbda264…7dd0
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
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
3 conflicts on slot 0x69c491e302…ce98d9
Audit this contract →
← previous block·next block →recent activity