pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,862,771
← previous block
next block →
recent activity
Analyzing
Block #89,862,771
10 transactions · 9 stateful · 2026-07-24 07:55:36 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,862,771
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x3f5c179b
#6
0x3f5c179b
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd73f8329…4803
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf0570aba…39fd
0x34b655…2a6f
4 touches
1 conflict
0xf2d0ab69…4b9e
0x34b655…2a6f
4 touches
1 conflict
0x496ff651…1310
0x34b655…2a6f
4 touches
1 conflict
0x74eeff73…4115
0x34b655…2a6f
3 touches
1 conflict
0xd1dd2e56…48f2
0x34b655…2a6f
3 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
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
0xd73f832912…a84803
Audit this contract →
← previous block
·
next block →
recent activity