pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,283,875
← previous block
next block →
recent activity
Analyzing
Block #91,283,875
11 transactions · 10 stateful · 2026-07-29 07:26:53 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,283,875
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
execFwdPositionOps
· blocks 1
#4
batchUpdate
#5
0x29eed2d3
#6
execFwdPositionOps
#7
0x6a69abb4
#8
setData
#9
execOrders
#10
0x59558d29
#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
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0xff3d91c4…1a37
0x34b655…2a6f
4 touches
1 conflict
0x8f888556…f387
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xbddcd9de…5d0b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
0x34b655…2a6f
3 touches
1 conflict
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
0x76ed8777f7…0c1e5f
Audit this contract →
← previous block
·
next block →
recent activity