pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,295,365
← previous block
next block →
recent activity
Analyzing
Block #87,295,365
9 transactions · 8 stateful · 2026-07-12 15:22:27 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,295,365
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
#3
0x0f6795d9
#4
supply
#5
0x0f6795d9
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe57232b3…0fbf
0x34b655…2a6f
4 touches
1 conflict
0x55c1a07a…51ea
0x34b655…2a6f
4 touches
1 conflict
0x00bbd28c…e227
0x34b655…2a6f
4 touches
1 conflict
0x19840da5…08b8
0x34b655…2a6f
4 touches
1 conflict
0x751349fe…0be8
0x34b655…2a6f
4 touches
1 conflict
0xb1acec7f…a6e8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xe57232b3f8…130fbf
Audit this contract →
← previous block
·
next block →
recent activity