pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,837,108
← previous block
next block →
recent activity
Analyzing
Block #85,837,108
12 transactions · 11 stateful · 2026-07-05 20:58:23 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,837,108
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
multicall
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x0f6795d9
#6
forward
#7
setData
#8
0x39435dac
· blocks 1
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#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
0x8ad89219…6f76
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x62341e2a…2d78
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0xc6101b5d…4361
0x3bd359…433a
2 touches
0 conflicts
0x5504f74a…6874
0x43cf54…7777
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
0x8ad8921926…246f76
Audit this contract →
← previous block
·
next block →
recent activity