pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,681,780
← previous block
next block →
recent activity
Analyzing
Block #93,681,780
11 transactions · 9 stateful · 2026-08-06 16:31:24 UTC
Parallelism
73
/100
Blocked
33
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,681,780
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x7af003…5086
#2
0x777de1…0fe6
#3
0x0c7abd22
#4
execOrders
· blocks 2
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
setData
#5
0x5acec890
· blocks 2
#6
0x5acec890
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x162ee430…31c3
0x34b655…2a6f
4 touches
1 conflict
0x5cc78005…4877
0x34b655…2a6f
2 touches
0 conflicts
0x7175a904…640c
0x34b655…2a6f
2 touches
0 conflicts
0x75f928fc…0465
0x34b655…2a6f
2 touches
0 conflicts
0x949c0ded…5cd3
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
0x033cf007c8…d2136d
Audit this contract →
← previous block
·
next block →
recent activity