pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,001,859
← previous block
next block →
recent activity
Analyzing
Block #92,001,859
8 transactions · 6 stateful · 2026-07-31 19:40:16 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,001,859
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execFwdPositionOps
· blocks 1
#4
execOrders
#5
execOrders
#6
0x6a6cfa98
#7
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcffc17bc…3544
0x34b655…2a6f
4 touches
1 conflict
0x13d41051…824c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x1e2721…7805
2 touches
0 conflicts
0x0e0c66fe…796f
0x1e2721…7805
2 touches
0 conflicts
0x0ddfdaf2…9e00
0x34b655…2a6f
2 touches
0 conflicts
0x0e8ecc8d…9695
0x34b655…2a6f
2 touches
0 conflicts
0x0eac7709…66c3
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
0xcffc17bcd7…af3544
Audit this contract →
← previous block
·
next block →
recent activity