pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,770,031
← previous block
next block →
recent activity
Analyzing
Block #91,770,031
10 transactions · 10 stateful · 2026-07-31 00:14:00 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,770,031
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0xa96df62f
#3
updatePrices
#4
0x0f6795d9
#5
0x39435dac
· blocks 2
#8
transfer
#9
0x59558d29
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xabe6698c…233b
0x34b655…2a6f
5 touches
3 conflicts
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0xff8cb0b2…ab78
0x34b655…2a6f
4 touches
1 conflict
0x40d2f403…d0bc
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity