pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,189,217
← previous block
next block →
recent activity
Analyzing
Block #85,189,217
9 transactions · 8 stateful · 2026-07-02 21:02:39 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,189,217
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x39435dac
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
#5
setData
#8
0xc7e3ec2c
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44564d6…bb43
0x34b655…2a6f
6 touches
3 conflicts
0x7a7bee69…6b65
0x34b655…2a6f
4 touches
1 conflict
0xcf7bbede…8ca1
0x34b655…2a6f
4 touches
1 conflict
0xd21c5532…77c4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeb4a203a…4dc4
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x72470f81…c402
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
3 conflicts on slot
0xb44564d6a3…0fbb43
Audit this contract →
← previous block
·
next block →
recent activity