pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,534,199
← previous block
next block →
recent activity
Analyzing
Block #92,534,199
10 transactions · 10 stateful · 2026-08-02 16:17:34 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,534,199
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
#5
0x6a6f6e16
#6
setData
#7
0x39435dac
· blocks 1
#9
0x59558d29
#4
0x0f6795d9
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf845b6ce…0547
0x34b655…2a6f
4 touches
1 conflict
0x03b16972…8f62
0x34b655…2a6f
4 touches
1 conflict
0x0535e9a3…bb9b
0x34b655…2a6f
4 touches
1 conflict
0x198f236d…9d00
0x34b655…2a6f
4 touches
1 conflict
0x3a22223a…b7dd
0x34b655…2a6f
4 touches
1 conflict
0x3a2a8323…3f40
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x71cbd5f6…e66e
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
1 conflict on slot
0xf845b6cedf…910547
Audit this contract →
← previous block
·
next block →
recent activity