pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,268,450
← previous block
next block →
recent activity
Analyzing
Block #91,268,450
9 transactions · 8 stateful · 2026-07-29 06:08:39 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,268,450
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
setData
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x69aed638…fbf5
0x34b655…2a6f
4 touches
1 conflict
0x78b60ad8…8468
0x34b655…2a6f
4 touches
1 conflict
0xa3244ff5…7cc1
0x34b655…2a6f
4 touches
1 conflict
0xa58f3b3b…97c8
0x34b655…2a6f
4 touches
1 conflict
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641e
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
0xe22ab637d9…007a8e
Audit this contract →
← previous block
·
next block →
recent activity