pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,759,883
← previous block
next block →
recent activity
Analyzing
Block #92,759,883
9 transactions · 9 stateful · 2026-08-03 11:13:48 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,759,883
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x4d8dc985
· blocks 2
#4
0x0f6795d9
#5
0x3f5c179b
#6
setData
#8
0xc7e3ec2c
#2
0x0f6795d9
· blocks 2
#3
0x0f6795d9
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bb455b5…6ed7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
4 touches
1 conflict
0x167ed203…48aa
0x34b655…2a6f
4 touches
1 conflict
0x7deb183c…0858
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
0x4bb455b534…336ed7
Audit this contract →
← previous block
·
next block →
recent activity