pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,309,533
← previous block
next block →
recent activity
Analyzing
Block #93,309,533
11 transactions · 11 stateful · 2026-08-05 09:20:00 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,309,533
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeb282f7f
#2
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
0x39435dac
#8
0x6a7300b7
#9
setData
#10
0x59558d29
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b482505…30c1
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xbf9a5632…9803
0x1efe02…37d6
2 touches
0 conflicts
0x06c2c8c1…c2a8
0x34b655…2a6f
2 touches
0 conflicts
0x06c2c8c1…c2a9
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275e
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275f
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
0x4b4825052a…4030c1
Audit this contract →
← previous block
·
next block →
recent activity