pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,128,841
← previous block
next block →
recent activity
Analyzing
Block #90,128,841
7 transactions · 7 stateful · 2026-07-25 06:18:29 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,128,841
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
0x0cf032c6
#4
setData
#5
execOrders
#6
0xc7e3ec2c
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfead7aed…ddfd
0x34b655…2a6f
4 touches
1 conflict
0x369a943e…aef6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x6254804c…a03b
0x34b655…2a6f
4 touches
1 conflict
0x62b26c37…87d6
0x34b655…2a6f
4 touches
1 conflict
0x74e0d9d2…47d7
0x34b655…2a6f
4 touches
1 conflict
0x850def09…120b
0x34b655…2a6f
4 touches
1 conflict
0x9816fc81…4f3c
0x34b655…2a6f
4 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
0xfead7aedbb…ccddfd
Audit this contract →
← previous block
·
next block →
recent activity