pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,433,536
← previous block
next block →
recent activity
Analyzing
Block #77,433,536
11 transactions · 9 stateful · 2026-05-27 22:39:30 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,433,536
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
batchUpdate
#2
batchUpdate
#3
0xb5ce855a
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
0x6a17731a
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x88bf5e75…0570
0x065c9d…c394
2 touches
0 conflicts
0x9182b9b8…9927
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0x045a4951…73a7
0x0a4fcb…a602
2 touches
0 conflicts
0x17caae1b…2ecf
0x0a4fcb…a602
2 touches
0 conflicts
0x7f9d640a…40f9
0x0a4fcb…a602
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity