pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,230,328
← previous block
next block →
recent activity
Analyzing
Block #93,230,328
10 transactions · 9 stateful · 2026-08-05 02:41:46 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,230,328
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3f5c179b
#2
0x0f6795d9
#3
0x57368ddf
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6a72a361
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd379a368…fea4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1fc046b…9af3
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x52ad6369…8a39
0x34b655…2a6f
4 touches
1 conflict
0x74137b07…5880
0x34b655…2a6f
3 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
2 touches
0 conflicts
0x1803586e…d149
0xa6afd3…d132
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
0xd379a36873…4efea4
Audit this contract →
← previous block
·
next block →
recent activity