pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,766,992
← previous block
next block →
recent activity
Analyzing
Block #91,766,992
10 transactions · 9 stateful · 2026-07-30 23:58:43 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,766,992
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0f6795d9
· blocks 2
#3
0x0f6795d9
#6
0x39435dac
#7
setData
#8
0x39435dac
#9
0x59558d29
#4
0x0f6795d9
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0bbe8ee6…4ede
0x34b655…2a6f
2 touches
0 conflicts
0x137fc090…814f
0x34b655…2a6f
2 touches
0 conflicts
0x2c3dbd78…1a68
0x34b655…2a6f
2 touches
0 conflicts
0x4bf59d22…00de
0x34b655…2a6f
2 touches
0 conflicts
0x706c758c…2fdb
0x34b655…2a6f
2 touches
0 conflicts
0x98212952…9ba6
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:
Perpl
1 conflict on slot
0xa4e9800f4e…fc4ab1
Audit this contract →
← previous block
·
next block →
recent activity