pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,000,003
← previous block
next block →
recent activity
Analyzing
Block #92,000,003
11 transactions · 10 stateful · 2026-07-31 19:30:56 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,000,003
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
matchOrders
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 2
#7
0x39435dac
#8
0x6a6cf868
#9
setData
#10
0x59558d29
#5
0x0f6795d9
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xa29a08f1…cdb0
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x0e0c66fe…796f
0x1e2721…7805
2 touches
0 conflicts
0x17530abf…5f20
0x754704…b603
2 touches
0 conflicts
0x1ea2c53b…887a
0x754704…b603
2 touches
0 conflicts
0x2edbccf6…cc14
0x754704…b603
2 touches
0 conflicts
0x431fa96d…6ac0
0x754704…b603
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
0x91b0f8edc5…b76bd7
Audit this contract →
← previous block
·
next block →
recent activity