pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,145,628
← previous block
next block →
recent activity
Analyzing
Block #96,145,628
9 transactions · 9 stateful · 2026-08-15 07:37:17 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,145,628
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0xcffefd2e
· blocks 2
#4
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#5
0xcffefd2e
#6
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf039e2f8…3d8a
0x34b655…2a6f
4 touches
1 conflict
0xa940f3a4…c5e8
0x34b655…2a6f
4 touches
1 conflict
0xb3e53c5e…b99c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe3c082c7…f032
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x4d6228eb…66e4
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
1 conflict on slot
0xf039e2f8da…b73d8a
Audit this contract →
← previous block
·
next block →
recent activity