pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,078,446
← previous block
next block →
recent activity
Analyzing
Block #92,078,446
10 transactions · 10 stateful · 2026-08-01 02:05:28 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,078,446
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x39435dac
#7
setData
#8
0x3f5c179b
#9
0x59558d29
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b55198a…b946
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01e4765d…2502
0x34b655…2a6f
2 touches
0 conflicts
0x153d1e25…10ea
0x34b655…2a6f
2 touches
0 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
2 touches
0 conflicts
0x3270d9f8…099a
0x34b655…2a6f
2 touches
0 conflicts
0x37141cb0…28ac
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
0x7b55198a70…73b946
Audit this contract →
← previous block
·
next block →
recent activity