pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,245,508
← previous block
next block →
recent activity
Analyzing
Block #93,245,508
12 transactions · 11 stateful · 2026-08-05 03:58:04 UTC
Parallelism
83
/100
Blocked
27
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,245,508
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x5acec890
· blocks 2
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#7
relay
#9
0x6a72b544
#10
setData
#11
execOrders
#3
0x5acec890
#6
0xed82b078
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71e1dee6…d11b
0x34b655…2a6f
4 touches
1 conflict
0xb6f18499…e5a2
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xda527a7a…8f76
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3de775b2…319b
0xa6afd3…d132
4 touches
1 conflict
0xfa551be3…a911
0xa6afd3…d132
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
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
0x71e1dee6d7…5bd11b
Audit this contract →
← previous block
·
next block →
recent activity