pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,947,905
← previous block
next block →
recent activity
Analyzing
Block #90,947,905
11 transactions · 9 stateful · 2026-07-28 03:14:57 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,947,905
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 2
#4
execFwdPositionOps
#6
0x3f5c179b
#7
execFwdPositionOps
#8
setData
#10
execOrders
#5
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0xd7e0d683…1f5a
0x34b655…2a6f
4 touches
1 conflict
0x6f900be0…cd6e
0x34b655…2a6f
4 touches
1 conflict
0x0aa169cf…80c7
0x34b655…2a6f
2 touches
0 conflicts
0x126a0344…4465
0x34b655…2a6f
2 touches
0 conflicts
0x160d7902…515b
0x34b655…2a6f
2 touches
0 conflicts
0x219c6953…c961
0x34b655…2a6f
2 touches
0 conflicts
0x2210c4e2…2ea9
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
0x957c875f2a…99b3f9
Audit this contract →
← previous block
·
next block →
recent activity