pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,568,175
← previous block
next block →
recent activity
Analyzing
Block #92,568,175
11 transactions · 10 stateful · 2026-08-02 19:08:25 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,568,175
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execFwdPositionOps
· blocks 2
#3
0x3f5c179b
#4
batchUpdate
#7
execFwdPositionOps
#8
setData
#9
execOrders
#10
execOrders
#5
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c6271e…70ea
0x34b655…2a6f
4 touches
1 conflict
0x6b89ce6f…cc35
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x65de6521…180f
0x065c9d…c394
2 touches
0 conflicts
0x7ef4ceca…7749
0x065c9d…c394
2 touches
0 conflicts
0xb18006ec…0adf
0x065c9d…c394
2 touches
0 conflicts
0xba650ef3…28ba
0x065c9d…c394
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
0x52c6271e07…f570ea
Audit this contract →
← previous block
·
next block →
recent activity