pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,755,883
← previous block
next block →
recent activity
Analyzing
Block #92,755,883
11 transactions · 10 stateful · 2026-08-03 10:53:40 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,755,883
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
· blocks 1
#3
0x0f6795d9
· blocks 1
#6
commit
#7
updateDataFeedsValuesPartial
#8
0xd708c5d8
#9
setData
#10
0xc7e3ec2c
#4
0x0f6795d9
#5
mergePositions
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb968c832…9b6a
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…0002
0x1e2721…7805
4 touches
1 conflict
0x0e0c66fe…796f
0x1e2721…7805
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0xb1b21ea8…d790
0x34b655…2a6f
4 touches
1 conflict
0x431fa96d…6ac0
0x754704…b603
4 touches
1 conflict
0xe96cbc90…be66
0x754704…b603
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:
0x99c7a72e…c78bf0
1 conflict on slot
0xb968c832a9…769b6a
Audit this contract →
← previous block
·
next block →
recent activity