pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,753,905
← previous block
next block →
recent activity
Analyzing
Block #92,753,905
13 transactions · 11 stateful · 2026-08-03 10:43:44 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,753,905
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
setData
#7
setData
#8
swap
#9
execOrders
· blocks 2
#10
execOrders
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
11
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xa36ea3e3…45d2
0x34b655…2a6f
4 touches
1 conflict
0xb42fe30c…8771
0x34b655…2a6f
4 touches
1 conflict
0xb6ea4726…5140
0x34b655…2a6f
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x56fed0dd…581f
0x34b655…2a6f
2 touches
0 conflicts
0x7e864dcb…418f
0x754704…b603
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity