pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,159,801
← previous block
next block →
recent activity
Analyzing
Block #92,159,801
9 transactions · 9 stateful · 2026-08-01 08:54:39 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,159,801
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#6
0x39435dac
#7
setData
#8
0x59558d29
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0x1a843f41…02aa
0x34b655…2a6f
4 touches
1 conflict
0x29c1a140…099f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4aaa2679…4c1d
0x34b655…2a6f
4 touches
1 conflict
0x7ba216b2…eec1
0x34b655…2a6f
4 touches
1 conflict
0x7ba216b2…eec2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
0xd29e547b5d…35a1dd
Audit this contract →
← previous block
·
next block →
recent activity