pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,503,596
← previous block
next block →
recent activity
Analyzing
Block #93,503,596
10 transactions · 8 stateful · 2026-08-06 01:35:40 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,503,596
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8263f5d9
#2
execOrders
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0xb2d4797b
#6
0x3f5c179b
· blocks 1
#9
setData
#7
batchUpdate
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19e49883…3293
0x851145…3f07
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
2 touches
0 conflicts
0x7c3d51a9…db35
0x34b655…2a6f
2 touches
0 conflicts
0x7c3d51a9…db36
0x34b655…2a6f
2 touches
0 conflicts
0x8369620c…4792
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:
0x851145ea…9f3f07
1 conflict on slot
0x19e49883af…1c3293
Audit this contract →
← previous block
·
next block →
recent activity