pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,580,096
← previous block
next block →
recent activity
Analyzing
Block #93,580,096
11 transactions · 11 stateful · 2026-08-06 08:00:13 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,580,096
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
#3
setData
#4
0x5acec890
· blocks 1
#5
0x5acec890
#6
updatePriceFeedsIfNecessary
#8
0x3f5c179b
#9
0x3f5c179b
#10
execFwdPositionOps
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03c38bff…f48f
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x7c1d804e…835c
0x34b655…2a6f
4 touches
1 conflict
0x7fa44fe8…484e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x2374f448…509f
0x065c9d…c394
2 touches
0 conflicts
0x5154eac8…f48b
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
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
0x03c38bff08…caf48f
Audit this contract →
← previous block
·
next block →
recent activity