pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,280,126
← previous block
next block →
recent activity
Analyzing
Block #93,280,126
13 transactions · 13 stateful · 2026-08-05 06:52:09 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,280,126
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0xb2d4797b
#6
batchUpdate
#7
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
#9
0x8b80a919
#10
0x6a72de10
#11
setData
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc21d7c…e062
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
2 touches
0 conflicts
0x334aa47d…cac0
0x34b655…2a6f
2 touches
0 conflicts
0x751f0341…fe9b
0x34b655…2a6f
2 touches
0 conflicts
0x91ace65b…97af
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
0xdfc21d7c53…51e062
Audit this contract →
← previous block
·
next block →
recent activity