pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,268,437
← previous block
next block →
recent activity
Analyzing
Block #93,268,437
10 transactions · 10 stateful · 2026-08-05 05:53:22 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
#93,268,437
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
0x3f5c179b
#3
executeBatch
#4
0x3f5c179b
#6
0x29eed2d3
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05ad0597…856d
0x34b655…2a6f
2 touches
0 conflicts
0x06e45d39…781e
0x34b655…2a6f
2 touches
0 conflicts
0x09790557…7c26
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x25932cec…cc11
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
0x5d1ac445db…e05233
Audit this contract →
← previous block
·
next block →
recent activity