pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,703,140
← previous block
next block →
recent activity
Analyzing
Block #90,703,140
8 transactions · 8 stateful · 2026-07-27 06:43:30 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,703,140
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x3f5c179b
#3
execFwdPositionOps
· blocks 1
#5
setData
#6
execOrders
#7
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30f2fc75…23ef
0x34b655…2a6f
4 touches
1 conflict
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x546d22…8146
2 touches
0 conflicts
0x00000000…003d
0x851145…3f07
2 touches
0 conflicts
0x42557d16…8439
0x851145…3f07
2 touches
0 conflicts
0xa386a1c7…027d
0x851145…3f07
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
0x30f2fc75b5…8d23ef
Audit this contract →
← previous block
·
next block →
recent activity