pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,399,658
← previous block
next block →
recent activity
Analyzing
Block #93,399,658
9 transactions · 9 stateful · 2026-08-05 16:53:08 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,399,658
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x5acec890
#3
execFwdPositionOps
#4
0x3f5c179b
#5
0x3f5c179b
· blocks 1
#7
execFwdPositionOps
#8
setData
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x46f4b57c…8d64
0x851145…3f07
4 touches
1 conflict
0x965c091f…4e3d
0x851145…3f07
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
2 touches
0 conflicts
0x3093e806…bde2
0x34b655…2a6f
2 touches
0 conflicts
0x428b6e5b…8909
0x34b655…2a6f
2 touches
0 conflicts
0x43e15ca4…039d
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity