pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,443,503
← previous block
next block →
recent activity
Analyzing
Block #91,443,503
11 transactions · 11 stateful · 2026-07-29 20:51:23 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,443,503
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
#3
0x6a6a6842
#4
execFwdPositionOps
· blocks 2
#6
execFwdPositionOps
· blocks 1
#7
execOrders
#8
setData
#10
0x59558d29
#5
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92115abd…ad76
0x34b655…2a6f
4 touches
1 conflict
0xa81d48e7…d003
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0x1a1c104d…a411
0x065c9d…c394
2 touches
0 conflicts
0xa77975dc…94c7
0x09475a…400f
2 touches
0 conflicts
0xc0240a50…d410
0x111111…db61
2 touches
0 conflicts
0xec3e20e7…e008
0x111111…db61
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
0x92115abda4…1fad76
Audit this contract →
← previous block
·
next block →
recent activity