pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,237,595
← previous block
next block →
recent activity
Analyzing
Block #93,237,595
11 transactions · 11 stateful · 2026-08-05 03:18:18 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,237,595
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrder
· blocks 1
#3
updatePrices
#7
0x3f5c179b
#8
execFwdPositionOps
#9
setData
#10
execOrders
#4
execFwdPositionOps
· blocks 2
#5
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbf36c8df…3bc1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xe2f7aa42…ae50
0x34b655…2a6f
4 touches
1 conflict
0xfe339dcb…de05
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
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
0x898d9b8ab1…f9d1ef
Audit this contract →
← previous block
·
next block →
recent activity