pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,163,424
← previous block
next block →
recent activity
Analyzing
Block #92,163,424
11 transactions · 11 stateful · 2026-08-01 09:12:52 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,163,424
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
execOrders
· blocks 1
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#7
execOrders
#8
setData
#10
0xc7e3ec2c
#6
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0x57b3b97e…7ca7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbfde0967…ce8e
0x34b655…2a6f
4 touches
1 conflict
0xdbd9d618…7b7e
0x34b655…2a6f
4 touches
1 conflict
0xdbd9d618…7b7f
0x34b655…2a6f
4 touches
1 conflict
0xe624cb16…9dc0
0x34b655…2a6f
4 touches
1 conflict
0xf007a4f4…507d
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
0xf9874e3690…90beed
Audit this contract →
← previous block
·
next block →
recent activity