pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,438,048
← previous block
next block →
recent activity
Analyzing
Block #93,438,048
11 transactions · 10 stateful · 2026-08-05 20:06:08 UTC
Parallelism
82
/100
Blocked
40
%
Avg conflicts / tx
0.36
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,438,048
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
execOrders
· blocks 1
#9
0x59558d29
· blocks 1
#2
matchOrders
#6
execFwdPositionOps
#8
execOrders
#10
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
7
w0
8
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x04a32684…1017
0x99c7a7…8bf0
4 touches
1 conflict
0x7445e790…b2fc
0x99c7a7…8bf0
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x70a7b5d6…fe0e
0x34b655…2a6f
4 touches
1 conflict
0x8a155597…2e0e
0x34b655…2a6f
4 touches
1 conflict
0x91cdfdeb…7feb
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity