pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,451,952
← previous block
next block →
recent activity
Analyzing
Block #93,451,952
12 transactions · 11 stateful · 2026-08-05 21:16:02 UTC
Parallelism
75
/100
Blocked
18
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,451,952
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
reallocate
#2
0xab083028
#3
0xab083028
#4
0x5acec890
#5
execFwdPositionOps
#6
placeAndExecuteMarketBuy
#7
execFwdPositionOps
#8
setData
#9
0x59558d29
· blocks 2
#10
0x59558d29
· blocks 1
#11
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1c9e5f70…b1c1
0x09475a…400f
2 touches
0 conflicts
0xafb857af…666b
0x09475a…400f
2 touches
0 conflicts
0xbd13703a…71fe
0x09475a…400f
2 touches
0 conflicts
0xc4f254e5…1b4b
0x09475a…400f
2 touches
0 conflicts
0x0c83ede5…b4f2
0xd5d960…eaee
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:
0x80c74517…647210
3 conflicts on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity