pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,514,179
← previous block
next block →
recent activity
Analyzing
Block #86,514,179
9 transactions · 7 stateful · 2026-07-09 00:18:19 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,514,179
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39435dac
#3
0x0f6795d9
· blocks 1
#4
0x6a4ee943
#5
setData
#6
0xe8adbf…f15d
#8
0x39435dac
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0xf967d7d8…d1e6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0899947a…48a7
0x34b655…2a6f
2 touches
0 conflicts
0x1fbe3441…7d6f
0x34b655…2a6f
2 touches
0 conflicts
0x3d4584df…ffed
0x34b655…2a6f
2 touches
0 conflicts
0x67185120…f565
0x34b655…2a6f
2 touches
0 conflicts
0x6b2ba712…0214
0x34b655…2a6f
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
0xefcdf19725…1096a2
Audit this contract →
← previous block
·
next block →
recent activity