pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,808,713
← previous block
next block →
recent activity
Analyzing
Block #94,808,713
10 transactions · 10 stateful · 2026-08-10 15:16:49 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,808,713
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5bf9264c
#2
0x5acec890
· blocks 1
#3
0x0f6795d9
· blocks 2
#5
0x3f5c179b
#7
transfer
#8
setData
· blocks 1
#4
0x0f6795d9
· blocks 1
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
6
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0db691ab…3ee3
0x34b655…2a6f
6 touches
3 conflicts
0xbaf079f2…2b96
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xca713a22…3083
0x34b655…2a6f
6 touches
3 conflicts
0x7523c6af…ea66
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x6c28863e…840e
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
0x0db691abac…993ee3
Audit this contract →
← previous block
·
next block →
recent activity