pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,515,845
← previous block
next block →
recent activity
Analyzing
Block #77,515,845
10 transactions · 9 stateful · 2026-05-28 07:47:49 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,515,845
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x6a17f39c
#5
setData
#6
execFwdPositionOps
· blocks 2
#7
execFwdPositionOps
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c3a0878…e481
0x34b655…2a6f
6 touches
3 conflicts
0x80630fb9…a436
0x34b655…2a6f
4 touches
1 conflict
0x9d0d44e0…88ad
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0xd1ef673a…e78a
0x34b655…2a6f
4 touches
1 conflict
0xd653c5b0…a35a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
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
0x6c3a087868…ffe481
Audit this contract →
← previous block
·
next block →
recent activity