pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,421,636
← previous block
next block →
recent activity
Analyzing
Block #92,421,636
12 transactions · 11 stateful · 2026-08-02 06:51:25 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,421,636
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOps
· blocks 1
#6
0xed82b078
#7
execOrders
#8
0x6a6ee965
#9
setData
#10
0x59558d29
· blocks 1
#5
execFwdPositionOps
#11
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0xd0b32ce7…083e
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0004
0x546d22…8146
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
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
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity