pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,541,388
← previous block
next block →
recent activity
Analyzing
Block #93,541,388
12 transactions · 10 stateful · 2026-08-06 04:45:38 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,541,388
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcbbdb31a
#2
matchOrders
#3
execOrders
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#6
placeAndExecuteMarketBuy
#8
claim
#9
0xed82b078
#10
0xed82b078
#11
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6997d36…4f33
0x34b655…2a6f
4 touches
1 conflict
0x44e8f9f4…a5ad
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
2 touches
0 conflicts
0x81da6711…3869
0x34b655…2a6f
2 touches
0 conflicts
0x87292c3e…5e25
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:
Perpl
1 conflict on slot
0xe6997d3634…504f33
Audit this contract →
← previous block
·
next block →
recent activity