pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,774,301
← previous block
next block →
recent activity
Analyzing
Block #85,774,301
11 transactions · 7 stateful · 2026-07-05 14:00:03 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,774,301
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3f5c179b
#2
forward
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x413cf0…68dc
#7
0xca6de8…a416
#8
0xa0b9f8…a11f
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…000b
0x24f29b…4337
2 touches
0 conflicts
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0xaeb5864c…7679
0x2a68ba…90c5
2 touches
0 conflicts
0x172b0de5…980b
0x34b655…2a6f
2 touches
0 conflicts
0x267e6f2b…14f2
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