pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,510,875
← previous block
next block →
recent activity
Analyzing
Block #90,510,875
6 transactions · 6 stateful · 2026-07-26 14:36:18 UTC
Parallelism
67
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,510,875
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
setData
#3
0x29eed2d3
· blocks 1
#5
execOrders
#4
0x29eed2d3
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
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0xbf554ced…3142
0x928dc8…8207
4 touches
1 conflict
0xbf554ced…3145
0x928dc8…8207
4 touches
1 conflict
0xbf554ced…3146
0x928dc8…8207
4 touches
1 conflict
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x22ac9edd…875a
0x34b655…2a6f
2 touches
0 conflicts
0x513b0c80…d2d9
0x34b655…2a6f
2 touches
0 conflicts
0x6e1d16c5…2d3e
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:
USDC (USDC)
1 conflict on slot
0x5311f86450…380984
Audit this contract →
← previous block
·
next block →
recent activity