pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,516,846
← previous block
next block →
recent activity
Analyzing
Block #89,516,846
12 transactions · 12 stateful · 2026-07-22 23:00:45 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,516,846
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postStateList
#2
0x98717539
#3
0x0f6795d9
· blocks 1
#4
metacall
#6
0x0f6795d9
#7
0x39435dac
#8
updateDataFeedsValuesPartial
#9
0x6a614c15
#10
setData
#11
0xc7e3ec2c
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0x2da28f…75e8
2 touches
0 conflicts
0x00000000…0003
0x2da28f…75e8
2 touches
0 conflicts
0xf334fe53…11d8
0x2da28f…75e8
2 touches
0 conflicts
0x0291b96b…587b
0x34b655…2a6f
2 touches
0 conflicts
0x4755fafb…859b
0x34b655…2a6f
2 touches
0 conflicts
0x4f7298fc…24db
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:
Perpl
1 conflict on slot
0xb3fb9fb561…7664db
Audit this contract →
← previous block
·
next block →
recent activity