pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,421,448
← previous block
next block →
recent activity
Analyzing
Block #91,421,448
12 transactions · 10 stateful · 2026-07-29 18:59:32 UTC
Parallelism
83
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,421,448
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
execFwdPositionOps
#4
forward
#5
claim
· blocks 1
#7
execFwdPositionOps
#8
setData
#9
0x34653439
#10
0x59558d29
· blocks 1
#3
execFwdPositionOps
#6
0xc925b3a5
#11
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w0
6
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0xc5d3b8ce…0068
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
3 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
2 touches
0 conflicts
0x5c56b0af…a9df
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004c
Audit this contract →
← previous block
·
next block →
recent activity