pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,223,091
← previous block
next block →
recent activity
Analyzing
Block #76,223,091
12 transactions · 10 stateful · 2026-05-22 08:16:03 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,223,091
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#6
0x6df9e92b
#7
0xe9316489
#8
setData
#10
execOrders
#11
execOrders
#5
fulfillWithERC20
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4c344860…c0d0
0x34b655…2a6f
2 touches
0 conflicts
0x8ed9c526…a5df
0x34b655…2a6f
2 touches
0 conflicts
0x24f37e11…9cb3
0x5afd3e…7620
2 touches
0 conflicts
0x8b9c040b…ce39
0x5afd3e…7620
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:
Liquidity Book Token (LBT)
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity