pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,611,089
← previous block
next block →
recent activity
Analyzing
Block #86,611,089
9 transactions · 7 stateful · 2026-07-09 11:07:51 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,611,089
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x957d4ba0
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x6a4f817f
#5
setData
#6
0x7902aa…dd93
#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
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x47d4745e…02bb
0x336ed4…c59c
2 touches
0 conflicts
0x4a870d86…79ef
0x336ed4…c59c
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x5a15b942…24f7
0x34b655…2a6f
2 touches
0 conflicts
0x5d006bcb…9e2e
0x34b655…2a6f
2 touches
0 conflicts
0x87ee379a…cd9e
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity