pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,813,295
← previous block
next block →
recent activity
Analyzing
Block #90,813,295
11 transactions · 11 stateful · 2026-07-27 15:57:46 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,813,295
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#3
0x3f5c179b
#4
setData
#5
execOrders
#6
execOrders
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#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
0xd4230a60…bd13
0x34b655…2a6f
4 touches
1 conflict
0x3ab787fc…6a13
0x34b655…2a6f
4 touches
1 conflict
0x00ac27e3…14ce
0x34b655…2a6f
2 touches
0 conflicts
0x0c233c18…37bc
0x34b655…2a6f
2 touches
0 conflicts
0x1dfc34bb…34e9
0x34b655…2a6f
2 touches
0 conflicts
0x1dfc34bb…34ea
0x34b655…2a6f
2 touches
0 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x428b6e5b…8909
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
0xd4230a6034…58bd13
Audit this contract →
← previous block
·
next block →
recent activity