pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,385,496
← previous block
next block →
recent activity
Analyzing
Block #91,385,496
12 transactions · 12 stateful · 2026-07-29 15:58:18 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,385,496
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
0xab083028
#4
updatePrices
#5
0x0f6795d9
· blocks 3
#8
batchUpdate
#9
0x0f6795d9
#10
setData
#6
0x0f6795d9
· blocks 1
#11
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc905883b…24a6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 conflicts
0x022a0545…065a
0x34b655…2a6f
5 touches
3 conflicts
0x5a90f30b…95fa
0x34b655…2a6f
4 touches
1 conflict
0x7281cd97…f967
0x34b655…2a6f
4 touches
1 conflict
0xa524a39b…df24
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:
Perpl
3 conflicts on slot
0xc905883b89…5924a6
Audit this contract →
← previous block
·
next block →
recent activity