pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,388,285
← previous block
next block →
recent activity
Analyzing
Block #93,388,285
11 transactions · 9 stateful · 2026-08-05 15:55:57 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,388,285
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0xeb282f7f
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
#7
batchCancelOrders
#9
setData
#10
0x59558d29
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaced930…08b5
0x34b655…2a6f
4 touches
1 conflict
0xcaced930…08b6
0x34b655…2a6f
4 touches
1 conflict
0x11dc5560…0c27
0x34b655…2a6f
4 touches
1 conflict
0x489a70d7…03cd
0x1efe02…37d6
2 touches
0 conflicts
0x03c38bff…f48f
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x454cdf57…aebc
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
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
0xcaced93001…5708b5
Audit this contract →
← previous block
·
next block →
recent activity