pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,983,383
← previous block
next block →
recent activity
Analyzing
Block #91,983,383
10 transactions · 8 stateful · 2026-07-31 18:07:21 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
#91,983,383
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 2
#3
handleOps
#5
0x39435dac
#6
0x39435dac
#7
0x6a6ce4d0
#8
setData
#9
0x59558d29
#2
0x0f6795d9
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427d1120…4eb1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x05475161…1bd5
0x34b655…2a6f
2 touches
0 conflicts
0x109e76c8…2d7c
0x34b655…2a6f
2 touches
0 conflicts
0x3812f5cf…b17a
0x34b655…2a6f
2 touches
0 conflicts
0x6ceb308b…3818
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
0x427d112082…7c4eb1
Audit this contract →
← previous block
·
next block →
recent activity