pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,411,549
← previous block
next block →
recent activity
Analyzing
Block #91,411,549
9 transactions · 8 stateful · 2026-07-29 18:09:44 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,411,549
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a6a4260
#2
updatePrices
#3
placeBet
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
0x6a6a4260
#8
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
0x34b655…2a6f
4 touches
1 conflict
0x49bfdd9d…fff5
0x34b655…2a6f
3 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
2 touches
0 conflicts
0xb9854153…ac42
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0002
0x48cba2…b48b
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
0xc824469a90…af641f
Audit this contract →
← previous block
·
next block →
recent activity