pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,511,490
← previous block
next block →
recent activity
Analyzing
Block #85,511,490
12 transactions · 9 stateful · 2026-07-04 08:48:52 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,511,490
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x0f6795d9
· blocks 1
#5
forward
#6
commit
#7
0x88134db2
#8
0x6a48c96c
#9
0x3f2c75…817d
#10
0xc9726f…4e8c
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9365e097…ff56
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x06ae1028…cbb5
0x34b655…2a6f
2 touches
0 conflicts
0x101c1cb0…6612
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
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
0x9365e0978e…fbff56
Audit this contract →
← previous block
·
next block →
recent activity