pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,944,379
← previous block
next block →
recent activity
Analyzing
Block #90,944,379
11 transactions · 10 stateful · 2026-07-28 02:57:13 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
#90,944,379
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
0x3f5c179b
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
execOrders
#8
setData
#9
0x03e61a62
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x112c35bc…2afc
0x34b655…2a6f
2 touches
0 conflicts
0x1b1451d3…e1f4
0x34b655…2a6f
2 touches
0 conflicts
0x21d22421…0b7a
0x34b655…2a6f
2 touches
0 conflicts
0x44d20f1a…1a1a
0x34b655…2a6f
2 touches
0 conflicts
0x673891f1…bf47
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
0xcc58c80b6c…80ff79
Audit this contract →
← previous block
·
next block →
recent activity