pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,059,460
← previous block
next block →
recent activity
Analyzing
Block #94,059,460
7 transactions · 7 stateful · 2026-08-08 00:10:56 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,059,460
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6b8f732b
#2
execFwdPositionOps
· blocks 1
#5
0x6a767488
#6
setData
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0cd9fc1…1c44
0x34b655…2a6f
4 touches
1 conflict
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1ca9a6de…019e
0x34b655…2a6f
2 touches
0 conflicts
0x6237f1a7…2f59
0x3bd359…433a
2 touches
0 conflicts
0xd9f1e40f…09a3
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x47bae1…7568
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
0xc0cd9fc147…b21c44
Audit this contract →
← previous block
·
next block →
recent activity