pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,553,878
← previous block
next block →
recent activity
Analyzing
Block #95,553,878
12 transactions · 11 stateful · 2026-08-13 05:59:20 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,553,878
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0xd60faa87
#3
0x0c7abd22
#4
execOrder
· blocks 1
#5
0x5acec890
#6
0x5acec890
#7
updateDataFeedsValuesPartial
#9
execFwdPositionOps
#10
setData
#11
0x59558d29
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d46eb2…d46b
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x0fc81850…e472
0x34b655…2a6f
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
2 touches
0 conflicts
0x446f2734…8b54
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
0xf3d46eb2e0…34d46b
Audit this contract →
← previous block
·
next block →
recent activity