pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,568,544
← previous block
next block →
recent activity
Analyzing
Block #91,568,544
12 transactions · 11 stateful · 2026-07-30 07:20:28 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
#91,568,544
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#3
execFwdPositionOps
#4
0x3f5c179b
#5
0x0c7abd22
#6
execFwdPositionOps
#7
execOrders
#8
execOrders
#9
0x6a6afbb3
#10
setData
#11
0x59558d29
#2
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
2 touches
0 conflicts
0x09a025d2…49ec
0x34b655…2a6f
2 touches
0 conflicts
0x12ba6be1…1126
0x34b655…2a6f
2 touches
0 conflicts
0x1dd79365…4bab
0x34b655…2a6f
2 touches
0 conflicts
0x2bbc37af…2efe
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
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity