pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,420,602
← previous block
next block →
recent activity
Analyzing
Block #93,420,602
11 transactions · 11 stateful · 2026-08-05 18:38:26 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,420,602
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
permit2TransferAndMulticall
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a73839a
#8
transfer
#9
setData
#10
execOrders
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ed8269b…cade
0x99c7a7…8bf0
4 touches
1 conflict
0x0ba2c03b…3d9f
0x754704…b603
4 touches
1 conflict
0x9b2b4ba7…f42d
0x754704…b603
4 touches
1 conflict
0xc07e7b41…7f0a
0x754704…b603
4 touches
1 conflict
0x3051f72d…943e
0x99c7a7…8bf0
4 touches
1 conflict
0x0dd3bdfb…7537
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3bdfb…7538
0x34b655…2a6f
2 touches
0 conflicts
0x110a671c…e284
0x34b655…2a6f
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:
0x99c7a72e…c78bf0
1 conflict on slot
0x7ed8269ba7…15cade
Audit this contract →
← previous block
·
next block →
recent activity