pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,718,780
← previous block
next block →
recent activity
Analyzing
Block #94,718,780
8 transactions · 8 stateful · 2026-08-10 07:42:59 UTC
Parallelism
50
/100
Blocked
38
%
Avg conflicts / tx
0.38
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,718,780
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x5acec890
· blocks 1
#4
redeemDelegations
#6
0x6a79817a
#7
setData
#2
0x5acec890
· blocks 1
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x182e11cf…8f19
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa60eabc0…9f8c
0x34b655…2a6f
4 touches
1 conflict
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4327afd2…1b3a
0x34b655…2a6f
2 touches
0 conflicts
0x6b556cfa…b5b1
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
0x182e11cf02…a88f19
Audit this contract →
← previous block
·
next block →
recent activity