pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,824,179
← previous block
next block →
recent activity
Analyzing
Block #90,824,179
11 transactions · 10 stateful · 2026-07-27 16:52:31 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,824,179
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#5
0x3f5c179b
#6
0x3f5c179b
#7
0x57368ddf
#8
0x6a678d46
#9
setData
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e0065ad…e39b
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b7ff287…d1ba
0x34b655…2a6f
2 touches
0 conflicts
0x0c27b92d…451b
0x34b655…2a6f
2 touches
0 conflicts
0x16eb5040…a048
0x34b655…2a6f
2 touches
0 conflicts
0x1e0c5c66…74d9
0x34b655…2a6f
2 touches
0 conflicts
0x24b08f9c…e594
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
0x3e0065ad02…f8e39b
Audit this contract →
← previous block
·
next block →
recent activity