pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,317,648
← previous block
next block →
recent activity
Analyzing
Block #87,317,648
12 transactions · 11 stateful · 2026-07-12 17:51:24 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
#87,317,648
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
· blocks 1
#3
0x6ad2e98b
#4
0x3f5c179b
#5
0x0f6795d9
#6
0x5339c59f
#7
0x0f6795d9
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
0x6a53d494
#11
setData
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x2b679442…d704
0x978ae7…7777
4 touches
1 conflict
0x67d846dd…358c
0x978ae7…7777
4 touches
1 conflict
0x103a49fa…87a8
0x9f3832…4ae4
4 touches
1 conflict
0x103a49fa…87a9
0x9f3832…4ae4
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xd96509de…24d9
0x9f3832…4ae4
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
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:
Wrapped MON (WMON)
1 conflict on slot
0x44ed742f98…3963f5
Audit this contract →
← previous block
·
next block →
recent activity