pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,961,997
← previous block
next block →
recent activity
Analyzing
Block #90,961,997
9 transactions · 9 stateful · 2026-07-28 04:25:49 UTC
Parallelism
56
/100
Blocked
33
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,961,997
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x5a5d9a99
#2
execFwdPositionOps
· blocks 3
#6
execOrders
#7
0x6a682fc5
#8
setData
#3
execFwdPositionOps
· blocks 2
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa38eb2fc…1659
0x34b655…2a6f
6 touches
3 conflicts
0xf7036f81…789a
0x34b655…2a6f
6 touches
3 conflicts
0x0285ddb3…6390
0x34b655…2a6f
6 touches
3 conflicts
0xa38eb2fc…1658
0x34b655…2a6f
6 touches
3 conflicts
0xfb6eb5df…6c71
0x34b655…2a6f
5 touches
3 conflicts
0x2e835e59…9c69
0x34b655…2a6f
5 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x07fee907…1c9b
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
3 conflicts on slot
0xa38eb2fcd4…781659
Audit this contract →
← previous block
·
next block →
recent activity