pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,311,393
← previous block
next block →
recent activity
Analyzing
Block #93,311,393
12 transactions · 10 stateful · 2026-08-05 09:29:21 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,311,393
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0xeb282f7f
#4
0x5acec890
· blocks 1
#5
0xddee77…4ac6
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
0x6a7302e8
#10
setData
#11
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xf3a15e46…4fa8
0x1efe02…37d6
2 touches
0 conflicts
0x278676c0…d15c
0x34b655…2a6f
2 touches
0 conflicts
0x325d8ae4…fac6
0x34b655…2a6f
2 touches
0 conflicts
0xbb97db90…4c93
0xc8689a…ee79
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
0x45ea7a9723…bdbbb3
Audit this contract →
← previous block
·
next block →
recent activity