pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,357,785
← previous block
next block →
recent activity
Analyzing
Block #93,357,785
11 transactions · 11 stateful · 2026-08-05 13:22:36 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,357,785
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0xa96df62f
#4
0x928e4afa
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
· blocks 1
#8
0x0f6795d9
#9
0xb2d4797b
#10
setData
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
2 touches
0 conflicts
0x7485f8af…7362
0x34b655…2a6f
2 touches
0 conflicts
0x8b76e9f2…54ee
0x34b655…2a6f
2 touches
0 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
2 touches
0 conflicts
0x8ff48740…c09a
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
0x4e8c4408ae…50d37b
Audit this contract →
← previous block
·
next block →
recent activity