pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,329,327
← previous block
next block →
recent activity
Analyzing
Block #93,329,327
12 transactions · 11 stateful · 2026-08-05 10:59:31 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,329,327
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postStateList
#2
0x5acec890
#3
0x5acec890
#4
0x3f5c179b
#5
executeBatch
#6
execFwdPositionOps
· blocks 1
#8
0x6a73180b
#9
setData
#10
0x9b3568…e054
#11
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0x369a943e…aef6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x37d710c8…45c1
0x34b655…2a6f
2 touches
0 conflicts
0x560b6fd9…a104
0x34b655…2a6f
2 touches
0 conflicts
0x5bc53470…8dde
0x34b655…2a6f
2 touches
0 conflicts
0x6939e474…4256
0x34b655…2a6f
2 touches
0 conflicts
0x8047e9b2…9bb8
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
0xb6ed511f4c…ab6b68
Audit this contract →
← previous block
·
next block →
recent activity