pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,782,043
← previous block
next block →
recent activity
Analyzing
Block #91,782,043
12 transactions · 11 stateful · 2026-07-31 01:14:27 UTC
Parallelism
75
/100
Blocked
27
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,782,043
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
· blocks 1
#6
execFwdPositionOps
#7
execOrders
#9
0x6a6bf76b
#10
setData
#5
batchUpdate
#8
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
8
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c16527f…628c
0x34b655…2a6f
4 touches
1 conflict
0xada16c69…5ab8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xa1bfcc4c…f2db
0x851145…3f07
4 touches
1 conflict
0xc1e685f7…7787
0x851145…3f07
4 touches
1 conflict
0xc2e36a04…b85e
0x851145…3f07
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
0x5c16527f85…5b628c
Audit this contract →
← previous block
·
next block →
recent activity