pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,686,792
← previous block
next block →
recent activity
Analyzing
Block #89,686,792
10 transactions · 8 stateful · 2026-07-23 17:07:41 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,686,792
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xb414539a
#4
execFwdPositionOps
· blocks 1
#6
0x6a624ad4
#7
setData
#8
execOrders
#9
execOrders
#3
0x6c05cd2b
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd43be87…f667
0xe1c8b7…3022
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb5f244d5…f550
0x34b655…2a6f
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xc6101b5d…4361
0x3bd359…433a
4 touches
1 conflict
0x5504f74a…6874
0x43cf54…7777
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:
0xe1c8b733…e33022
1 conflict on slot
0xdd43be87b3…92f667
Audit this contract →
← previous block
·
next block →
recent activity