pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,294,772
← previous block
next block →
recent activity
Analyzing
Block #91,294,772
8 transactions · 8 stateful · 2026-07-29 08:21:43 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,294,772
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
#3
0x6a69b88f
#4
setData
#5
0x59558d29
· blocks 1
#7
0xc7e3ec2c
#6
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x064f7a79…f8eb
0x34b655…2a6f
2 touches
0 conflicts
0x15437606…7ec7
0x34b655…2a6f
2 touches
0 conflicts
0x24b08f9c…e594
0x34b655…2a6f
2 touches
0 conflicts
0x2f058af7…9d8f
0x34b655…2a6f
2 touches
0 conflicts
0x2fd12b6c…02cc
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…00004b
Audit this contract →
← previous block
·
next block →
recent activity