pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,847,830
← previous block
next block →
recent activity
Analyzing
Block #89,847,830
10 transactions · 7 stateful · 2026-07-24 06:40:27 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,847,830
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd60faa87
· blocks 1
#3
0x5a5d9a99
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x0f6795d9
#7
0xce1e7030
#8
setData
#9
exactInputSingle
#2
0x693c2be6
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x04ddf6…7f33
4 touches
1 conflict
0x00000000…0003
0x04ddf6…7f33
4 touches
1 conflict
0xaeabffea…5dd4
0x0a3323…0a3c
4 touches
1 conflict
0x6901bef4…4a69
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x04ddf6…7f33
4 touches
1 conflict
0x75f6ea6f…ae4c
0x0a3323…0a3c
2 touches
0 conflicts
0x182e11cf…8f19
0x34b655…2a6f
2 touches
0 conflicts
0x1de49243…4aa3
0x34b655…2a6f
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:
0x04ddf65a…767f33
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity