pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,295,671
← previous block
next block →
recent activity
Analyzing
Block #91,295,671
10 transactions · 10 stateful · 2026-07-29 08:26:14 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,295,671
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
#3
0x0f6795d9
#4
0x6a69b99e
#5
setData
#6
0x39435dac
· blocks 2
#9
0x59558d29
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb874a6c…caa0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbca4de0c…577c
0x34b655…2a6f
4 touches
1 conflict
0xbff51dea…acfa
0x34b655…2a6f
4 touches
1 conflict
0xdf25e257…25a0
0x34b655…2a6f
4 touches
1 conflict
0xfcfe96e7…4a4d
0x34b655…2a6f
4 touches
1 conflict
0x5f43f2bc…e94f
0x34b655…2a6f
4 touches
1 conflict
0x2a24af1d…7be1
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
0xfb874a6c9f…bfcaa0
Audit this contract →
← previous block
·
next block →
recent activity