pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,691,726
← previous block
next block →
recent activity
Analyzing
Block #89,691,726
10 transactions · 10 stateful · 2026-07-23 17:32:34 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,691,726
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5a5d9a99
· blocks 1
#4
0x3f5c179b
#5
0x1fe271b4
· blocks 1
#7
0xed82b078
#8
forward
#9
setData
#3
execFwdPositionOps
#6
0x1fe271b4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0267b653…ea41
0x0a2fbf…29b1
4 touches
1 conflict
0xde040102…ea77
0x0a2fbf…29b1
4 touches
1 conflict
0xde040102…ea78
0x0a2fbf…29b1
4 touches
1 conflict
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0x1bff683e…7ecb
0x754704…b603
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
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:
0x0a2fbf2d…f729b1
1 conflict on slot
0x0267b6537d…3dea41
Audit this contract →
← previous block
·
next block →
recent activity