pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,238,651
← previous block
next block →
recent activity
Analyzing
Block #90,238,651
9 transactions · 9 stateful · 2026-07-25 15:31:58 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,238,651
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute302
#2
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#6
setData
#7
execOrders
· blocks 1
#5
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x446f2734…8b54
0x0a3323…0a3c
2 touches
0 conflicts
0x52c63247…ce02
0x0a3323…0a3c
2 touches
0 conflicts
0x0181bb37…6628
0x34b655…2a6f
2 touches
0 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
2 touches
0 conflicts
0x25f585e3…7915
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
0x0000000000…0000c9
Audit this contract →
← previous block
·
next block →
recent activity