pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,489,499
← previous block
next block →
recent activity
Analyzing
Block #87,489,499
9 transactions · 7 stateful · 2026-07-13 13:00:37 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,489,499
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a54e1ed
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x3f5c179b
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
· blocks 1
#8
0x6a54e1ed
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa31caf43…1ade
0x34b655…2a6f
4 touches
1 conflict
0x1c559d10…5e3c
0x34b655…2a6f
4 touches
1 conflict
0x7548b289…f0dc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x88adad52…54b7
0x34b655…2a6f
4 touches
1 conflict
0xa31caf43…1add
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
0xa31caf43a1…681ade
Audit this contract →
← previous block
·
next block →
recent activity