pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,681,684
← previous block
next block →
recent activity
Analyzing
Block #90,681,684
7 transactions · 7 stateful · 2026-07-27 04:55:34 UTC
Parallelism
71
/100
Blocked
29
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,681,684
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
0x6a66e53e
#4
setData
#5
execOrders
· blocks 1
#2
execFwdPositionOps
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6884b1c…8b7f
0x34b655…2a6f
4 touches
1 conflict
0x53f7214d…8ec6
0x34b655…2a6f
4 touches
1 conflict
0xf2e7ad97…a370
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot
0xf6884b1c10…e88b7f
Audit this contract →
← previous block
·
next block →
recent activity