pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,806,616
← previous block
next block →
recent activity
Analyzing
Block #94,806,616
11 transactions · 7 stateful · 2026-08-10 15:06:16 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,806,616
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
0x4c38f2…1eaa
#3
execOrder
· blocks 1
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
execOrders
#9
0x6a79e960
#10
depositTo
#4
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x183a32c3…5ef2
0x34b655…2a6f
2 touches
0 conflicts
0x18c53a40…8bd0
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x2145086e…39c6
0x34b655…2a6f
2 touches
0 conflicts
0x2b5101ac…090b
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
0xb3fb9fb561…7664db
Audit this contract →
← previous block
·
next block →
recent activity