pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,991,249
← previous block
next block →
recent activity
Analyzing
Block #90,991,249
9 transactions · 9 stateful · 2026-07-28 06:53:03 UTC
Parallelism
78
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,991,249
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execFwdPositionOps
· blocks 3
#3
executeBatch
#7
0xe9316489
#8
setData
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3c9b04f…1db4
0x34b655…2a6f
4 touches
1 conflict
0x03fe94de…ffc8
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x18e86f02…fa98
0x34b655…2a6f
4 touches
1 conflict
0x289e1312…27b0
0x34b655…2a6f
4 touches
1 conflict
0x2d3930d3…c9b8
0x34b655…2a6f
4 touches
1 conflict
0x2f8f103b…29f4
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
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
0xe3c9b04f60…541db4
Audit this contract →
← previous block
·
next block →
recent activity