pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,556,502
← previous block
next block →
recent activity
Analyzing
Block #92,556,502
8 transactions · 8 stateful · 2026-08-02 18:09:43 UTC
Parallelism
63
/100
Blocked
38
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,556,502
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
· blocks 3
#6
setData
#7
0x59558d29
#3
0x5acec890
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x913f9580…d507
0x34b655…2a6f
4 touches
1 conflict
0x6a192d91…d497
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x171d9a84…b3b7
0x34b655…2a6f
2 touches
0 conflicts
0x1b9f1c76…23d5
0x34b655…2a6f
2 touches
0 conflicts
0x21d05894…b693
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
3 conflicts on slot
0xa558e11562…cafc88
Audit this contract →
← previous block
·
next block →
recent activity