pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,088,614
← previous block
next block →
recent activity
Analyzing
Block #88,088,614
10 transactions · 8 stateful · 2026-07-16 07:48:36 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,088,614
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x7d2c3ba9
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
0x0f6795d9
#8
setData
#9
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5777bd87…71bd
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x16f5792d…f853
0x000000…012a
2 touches
0 conflicts
0x88f12095…2334
0x000000…012a
2 touches
0 conflicts
0xe7fa6db5…a6d4
0x000000…012a
2 touches
0 conflicts
0x3918c64d…b3bd
0x34b655…2a6f
2 touches
0 conflicts
0x60dd8364…43d8
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
0x5777bd874f…7071bd
Audit this contract →
← previous block
·
next block →
recent activity