pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,618,840
← previous block
next block →
recent activity
Analyzing
Block #86,618,840
10 transactions · 9 stateful · 2026-07-09 11:59:36 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,618,840
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x0f6795d9
#5
0x3f5c179b
· blocks 1
#7
setData
#8
0x34653439
#9
0x39435dac
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfadb0e19…7a27
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x42c33c06…f6a3
0x34b655…2a6f
2 touches
0 conflicts
0x5efa0d16…4a5d
0x34b655…2a6f
2 touches
0 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
2 touches
0 conflicts
0x89999c15…fdac
0x34b655…2a6f
2 touches
0 conflicts
0x9c540cb6…ea0c
0x34b655…2a6f
2 touches
0 conflicts
0xcd81cc7b…8da0
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:
0x851145ea…9f3f07
1 conflict on slot
0xfadb0e1920…d17a27
Audit this contract →
← previous block
·
next block →
recent activity