pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,420,107
← previous block
next block →
recent activity
Analyzing
Block #92,420,107
11 transactions · 11 stateful · 2026-08-02 06:43:44 UTC
Parallelism
82
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,420,107
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
0x5acec890
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#7
setData
#8
0x59558d29
· blocks 1
#10
0xc7e3ec2c
#3
0x5acec890
#6
0x0f6795d9
#9
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01a08f7d…dec6
0x34b655…2a6f
4 touches
1 conflict
0x9c4ca661…944d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcc6d0014…6cf4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x14f57d50…3187
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
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
0x01a08f7dea…2ddec6
Audit this contract →
← previous block
·
next block →
recent activity